List all generated guide files in the codeglance-analysis/guide directory.
AI agents call list_generated_guides to retrieve information from Codeglance without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about existing guide files from a directory without modifying, deleting, executing code, or creating financial obligations. It has minimal blast radius if misused—at worst, an AI agent would learn what guides exist. No data is altered or operations triggered.
From the tool's definition Tool name 'list_generated_guides' and description 'List all generated guide files' indicate a retrieval operation with no side effects. The verb 'list' is explicitly categorized as a Read operation per the classification rules.
Attacks that exploit this kind of access
List all generated guide files in the codeglance-analysis/guide directory. It is categorised as a Read tool in the Codeglance MCP Server, which means it retrieves data without modifying state.
Register the Codeglance MCP server in PolicyLayer and add a rule for list_generated_guides: 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 Codeglance. Nothing to install.
list_generated_guides 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 list_generated_guides 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 list_generated_guides. 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.
list_generated_guides is provided by the Codeglance MCP server (lucidopus/codeglance-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 →