Get the skeleton of a Python file — all public function and class names,
AI agents call get_signature to retrieve information from Codevira MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that queries and returns structural metadata (function and class signatures) from a Python file without altering any data or executing code. It is a pure information retrieval operation with no side effects, fitting the Read category.
From the tool's definition Tool name is 'get_signature' and description states it retrieves 'the skeleton of a Python file — all public function and class names' with no modifications or side effects.
Documented attack patterns abuse exactly the kind of access get_signature gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Codevira MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_signature:
{
"version": "1",
"default": "deny",
"tools": {
"get_signature": {}
}
}get_signature is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the skeleton of a Python file — all public function and class names,. It is categorised as a Read tool in the Codevira MCP MCP Server, which means it retrieves data without modifying state.
Register the Codevira MCP server in PolicyLayer and add a rule for get_signature: 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 Codevira MCP. Nothing to install.
get_signature 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_signature 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_signature. 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_signature is provided by the Codevira MCP server (sachinshelke/codevira). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Codevira MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
48 Codevira MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.