AI agents call list-tools to retrieve information from Dynamic MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about available tools without creating, modifying, deleting, or executing anything. It is a straightforward enumeration/listing operation typical of Read category tools. The low severity reflects minimal risk—disclosure of tool availability is generally less sensitive than data manipulation or code execution.
From the tool's definition Tool name 'list-tools' and description 'List all tools' indicate a data retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access list-tools gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Dynamic MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list-tools:
{
"version": "1",
"default": "deny",
"tools": {
"list-tools": {}
}
} list-tools is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all tools. It is categorised as a Read tool in the Dynamic MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Dynamic MCP Server MCP server in PolicyLayer and add a rule for list-tools: 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 Dynamic MCP Server. Nothing to install.
list-tools is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list-tools 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.
Set action: deny in the PolicyLayer policy for list-tools. 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.
list-tools is provided by the Dynamic MCP Server MCP server (scitara-cto/dynamic-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Dynamic MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 Dynamic MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.