Get information about methods in a proto file
AI agents call getMethodInformation to retrieve information from gRPC MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves metadata about gRPC methods defined in Protocol Buffer files. It has no side effects—it does not execute RPC calls, modify files, delete data, or trigger external operations. It is purely informational retrieval, fitting the 'Read' category. Severity is low because exposing method signatures and metadata poses minimal risk even if an AI agent queries it unnecessarily.
From the tool's definition Tool name 'getMethodInformation' and description 'Get information about methods in a proto file' indicate data retrieval only. The verb 'Get' and context of retrieving proto file metadata show no modification, deletion, or execution of arbitrary code.
Attacks that exploit this kind of access
Get information about methods in a proto file. It is categorised as a Read tool in the gRPC MCP Server MCP Server, which means it retrieves data without modifying state.
Register the gRPC MCP Server MCP server in PolicyLayer and add a rule for getMethodInformation: 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 gRPC MCP Server. Nothing to install.
getMethodInformation 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 getMethodInformation 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 getMethodInformation. 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.
getMethodInformation is provided by the gRPC MCP Server MCP server (yuki4-dev/grpc-mcp). 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 →