This record as markdown: /tools/io-github-devopam-mcpg/describe-self.md
What describe_self does on Mcpg
AI agents call describe_self 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_self is rated Low
The name pattern 'describe_*' typically indicates a query or inspection operation that returns information about the system without modifying or executing anything. Given the PostgreSQL MCP server context and the absence of any destructive or side-effect indicators, this is classified as a Read operation.
From the tool's definition Tool name 'describe_self' suggests metadata retrieval or introspection about the server's capabilities, with no parameters indicated.
Attacks that exploit this kind of access
The rule that runs describe_self 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_self, this is the rule to start with:
describe_self 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_self call is checked against it from then on.
Questions about describe_self
describe_self 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_self: 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_self 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_self 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_self. 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_self 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