AI agents call list_all_tools to retrieve information from Medwriter without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward metadata retrieval tool that provides information about available capabilities. It has no side effects, does not execute code or external operations, does not modify data, and does not delete anything.
From the tool's definition The tool name is 'list_all_tools' and the description states it 'List all available tools in the Medical Writer's AI Toolkit with tier and description.' This is a query operation that retrieves and enumerates available tools without modifying, executing, or…
Attacks that exploit this kind of access
List all available tools in the Medical Writer's AI Toolkit with tier and description. It is categorised as a Read tool in the Medwriter MCP Server, which means it retrieves data without modifying state.
Register the Medwriter MCP server in PolicyLayer and add a rule for list_all_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 Medwriter. Nothing to install.
list_all_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_all_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_all_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_all_tools is provided by the Medwriter MCP server (pubspro/medwriter-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →