This record as markdown: /tools/io-github-devopam-mcpg/describe-tool.md
What describe_tool does on Mcpg
AI agents call describe_tool to retrieve information from Mcpg without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why describe_tool is rated Low
The name 'describe_tool' typically indicates a Read operation that returns information about a tool's signature, parameters, or documentation. No side effects, modifications, or external operations are implied. The empty description lowers confidence somewhat, but the naming convention strongly suggests a read-only introspection capability typical in database/API tools.
From the tool's definition Tool name 'describe_tool' suggests it retrieves or queries metadata/documentation about tools without modifying state. Description is empty, reducing confidence.
Attacks that exploit this kind of access
The rule that runs describe_tool safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcpg, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For describe_tool, this is the rule to start with:
describe_tool is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcpg, apply this rule, and every describe_tool call is checked against it from then on.
Questions about describe_tool
describe_tool is a read tool on the Mcpg MCP server. It is categorised as a Read tool in the Mcpg MCP Server, which means it retrieves data without modifying state.
Register the Mcpg MCP server in PolicyLayer and add a rule for describe_tool: 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 Mcpg. Nothing to install.
describe_tool 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 describe_tool 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 describe_tool. 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.
describe_tool is provided by the Mcpg MCP server (pypi:mcpg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcpg, and thousands of servers like it.
This server
Across the catalogue