Low Risk

agent_tools_list

List all registered agent runtime tools

Part of the Vibecheck server.

agent_tools_list is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE VIBECHECK →

Free to start. No card required.

AI agents call agent_tools_list to retrieve information from Vibecheck 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 agent_tools_list 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "agent_tools_list": {}
  }
}

See the full Vibecheck policy for all 103 tools.

Get this rule live on your own Vibecheck server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY VIBECHECK →

View all 103 tools →

These attack patterns abuse exactly the kind of access agent_tools_list gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so agent_tools_list only ever does what you allow.

SECURE VIBECHECK →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the agent_tools_list tool do? +

List all registered agent runtime tools. It is categorised as a Read tool in the Vibecheck MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on agent_tools_list? +

Register the Vibecheck MCP server in PolicyLayer and add a rule for agent_tools_list: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Vibecheck. Nothing to install.

What risk level is agent_tools_list? +

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

Can I rate-limit agent_tools_list? +

Yes. Add a rate_limit block to the agent_tools_list rule in your PolicyLayer 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 agent_tools_list completely? +

Set action: deny in the PolicyLayer policy for agent_tools_list. 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 agent_tools_list? +

agent_tools_list is provided by the Vibecheck MCP server (@vibecheckdev/vibecheck-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Vibecheck tool call.

Deterministic rules across all 103 Vibecheck tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.