AI agents call get_mcp_details to retrieve information from Mcpcute without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves details about MCP servers—a query/fetch operation with no side effects. It does not create, modify, delete, or execute anything. It is a Read operation with minimal blast radius if misused by an AI agent (returns information only). The constraint '[EXPLICIT ONLY - Do NOT use unless the user explicitly mentions...]' in the description further confirms it is a passive information retrieval tool.
From the tool's definition Tool name 'get_mcp_details' and description pattern match retrieval operations. Part of a 3-tool aggregator alongside 'search' and 'get_details' (read operations) and 'execute' (separate, distinct tool).
Attacks that exploit this kind of access
[EXPLICIT ONLY - Do NOT use unless the user explicitly mentions. It is categorised as a Read tool in the Mcpcute MCP Server, which means it retrieves data without modifying state.
Register the Mcpcute MCP server in PolicyLayer and add a rule for get_mcp_details: 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 Mcpcute. Nothing to install.
get_mcp_details 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 get_mcp_details 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 get_mcp_details. 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.
get_mcp_details is provided by the Mcpcute MCP server (zhigang1992/mcpcute). 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 →