Get parameters and examples for a given apiId. Call before executeApi to confirm required params.
AI agents call getApiDetails to retrieve information from Dynamic API Server (MCP) without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only tool that queries metadata about available APIs. It has no side effects, does not execute external operations, and does not modify any state. The purpose is purely informational—to help callers understand what parameters an API requires before calling executeApi. The blast radius of misuse is minimal since retrieving API documentation cannot cause harm.
From the tool's definition Tool name 'getApiDetails' and description 'Get parameters and examples for a given apiId' indicate it retrieves information about API specifications without modifying or executing any operations.
Attacks that exploit this kind of access
Get parameters and examples for a given apiId. Call before executeApi to confirm required params. It is categorised as a Read tool in the Dynamic API Server (MCP) MCP Server, which means it retrieves data without modifying state.
Register the Dynamic API Server (MCP) MCP server in PolicyLayer and add a rule for getApiDetails: 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 Dynamic API Server (MCP). Nothing to install.
getApiDetails 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 getApiDetails 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 getApiDetails. 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.
getApiDetails is provided by the Dynamic API Server (MCP) MCP server (1049861657/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
getApiDetails is one line of Dynamic API Server (MCP)'s registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →