get_tool_details
AI agents call get_tool_details to retrieve information from Ultimate-MCP-Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name strongly suggests a read-only operation that retrieves or queries metadata about available tools. With no description to confirm side effects, the conservative interpretation based on the naming pattern ('get_*') places this in the Read category. Severity is low because retrieving tool metadata poses minimal risk—it provides information but does not modify, delete, or execute operations.
From the tool's definition Tool name 'get_tool_details' indicates retrieval of information about tools. No description provided, but the name and context (within a suite of tools for agent orchestration and token optimization) suggest a query/lookup operation.
Attacks that exploit this kind of access
get_tool_details. It is categorised as a Read tool in the Ultimate-MCP-Server MCP Server, which means it retrieves data without modifying state.
Register the Ultimate-MCP-Server 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 Ultimate-MCP-Server. 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 Ultimate-MCP-Server MCP server (logos-parthenos-ai/ultimate_mcp_server). 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 →