Agents, skills, and MCP

Review local skills and MCP servers and verify their protection state.

Patronus discovers supported local skill files and MCP configurations. Discovery shows that an asset exists; runtime evidence shows how it was used.

Review a skill

Open the local assets view and inspect a skill’s source, review state, and any security annotations. A new skill may need acknowledgement. A changed skill needs another review because its instructions may differ from the version you accepted.

Acknowledging a skill records the review. It does not mark future tool calls safe or bypass runtime policy.

Monitor an MCP server

Find the server in the local assets view and check its source client and configuration.
Choose Monitor when offered. Patronus prepares the supported local protection route.
Check the resulting state. Monitor pending is not the same as Monitored.
Restart the MCP client if needed to load its changed configuration, then make a harmless tool call.
Inspect the resulting trace and policy decisions.

For stdio servers, Patronus uses a local gateway between the client and the server. HTTP-based MCP also depends on the supported routing and inspection path. See MCP integration.

Handle changes

If an asset shows Changed or Drift, inspect what changed before acknowledging it or selecting Accept drift. A changed skill or monitored MCP route can affect whether subsequent activity is allowed.

Ignore changes the local asset’s protection state. It is not a general allow policy for every request from that agent.

Discovery limits

Discovery covers supported files and configurations, not every installed agent. Observed tool lists and calls become runtime evidence. See integrations for client compatibility and plugins.