list_catalog_tools
AI agents call list_catalog_tools to retrieve information from Mdb Mcp Gateway without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries information about available tools in the catalog without modifying any data or triggering external operations. It fits the Read category as a discovery/introspection mechanism. Low severity because listing tools has minimal blast radius—it provides metadata only, with no side effects on data, execution, or financial systems.
From the tool's definition Tool name 'list_catalog_tools' indicates a listing/enumeration operation with no modification capability. Absence of description lowers confidence slightly, but the name strongly suggests read-only introspection of available tools.
Attacks that exploit this kind of access
list_catalog_tools. It is categorised as a Read tool in the Mdb Mcp Gateway MCP Server, which means it retrieves data without modifying state.
Register the Mdb Mcp Gateway MCP server in PolicyLayer and add a rule for list_catalog_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 Mdb Mcp Gateway. Nothing to install.
list_catalog_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_catalog_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_catalog_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_catalog_tools is provided by the Mdb Mcp Gateway MCP server (ranfysvalle02/m-gate). 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 →