Analyze file, function, or class. Returns structured JSON for AI consumption.
AI agents call gid_analyze to retrieve information from GID MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs static analysis and querying of a graph-based software architecture representation. It retrieves information about code structure without creating, modifying, deleting, or executing anything. The output is structured data for consumption, typical of Read category tools. No side effects or state changes are indicated.
From the tool's definition Tool description states 'Analyze file, function, or class. Returns structured JSON for AI consumption.' The verb 'analyze' and the fact that it 'returns' data with no mention of modification, deletion, or execution indicates a read-only operation that…
Attacks that exploit this kind of access
Analyze file, function, or class. Returns structured JSON for AI consumption. It is categorised as a Read tool in the GID MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GID MCP Server MCP server in PolicyLayer and add a rule for gid_analyze: 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 GID MCP Server. Nothing to install.
gid_analyze 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 gid_analyze 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 gid_analyze. 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.
gid_analyze is provided by the GID MCP Server MCP server (potatouniverse/graph-indexed-development-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 →