AI agents call get_tool_details to retrieve information from Disvr without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves metadata about MCP tools (installation info, environment variables, function signatures). It performs no data modification, deletion, code execution, or financial operations. The action is purely informational lookup with no side effects on the discovered tools themselves.
From the tool's definition Tool description states 'Get full details for a specific tool, including install instructions, required environment variables, and available tool functions.' The verbs 'get' and 'details' indicate retrieval of information without modification or execution of…
Attacks that exploit this kind of access
Get full details for a specific tool, including install instructions, required environment variables, and available tool functions. It is categorised as a Read tool in the Disvr MCP Server, which means it retrieves data without modifying state.
Register the Disvr MCP server in PolicyLayer and add a rule for get_tool_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 Disvr. Nothing to install.
get_tool_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_tool_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_tool_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_tool_details is provided by the Disvr MCP server (svanik-yan/disvr). 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 →