Low Risk

guard_list_agents

List all Guard-registered agents for the current user. Each object contains: agent_id -- UUID; input for guard_get_profile, guard_update_agent, guard_delete_agent agent_name, runtime, description status -- "active" | "paused" (budget exhausted) | "deactivated" budget_usd, s...

Part of the Clevername MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call guard_list_agents to retrieve information from Clevername without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though guard_list_agents only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

clevername.yaml
tools:
  guard_list_agents:
    rules:
      - action: allow

See the full Clevername policy for all 67 tools.

Tool Name guard_list_agents
Category Read
Risk Level Low

View all 67 tools →

Agents calling read-class tools like guard_list_agents have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the guard_list_agents tool do? +

List all Guard-registered agents for the current user. Each object contains: agent_id -- UUID; input for guard_get_profile, guard_update_agent, guard_delete_agent agent_name, runtime, description status -- "active" | "paused" (budget exhausted) | "deactivated" budget_usd, spend_mtd -- monthly cap and current spend USD allowed_models, pii_mode, key_interception_enabled, rate_limit_rpm token_id -- UUID; input for guard_revoke_token (NOT the cnk_* string) token_hint -- first 8 chars of the active cnk_* token (match to find the right token) created_at, updated_at. It is categorised as a Read tool in the Clevername MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on guard_list_agents? +

Add a rule in your Intercept YAML policy under the tools section for guard_list_agents. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Clevername MCP server.

What risk level is guard_list_agents? +

guard_list_agents is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit guard_list_agents? +

Yes. Add a rate_limit block to the guard_list_agents rule in your Intercept policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block guard_list_agents completely? +

Set action: deny in the Intercept policy for guard_list_agents. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides guard_list_agents? +

guard_list_agents is provided by the Clevername MCP server (@clevername/clevername-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Clevername

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.