list_projects
AI agents call list_projects to retrieve information from Keshro MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
List/enumerate operations are Read-category tools. They query and return data without modifying, deleting, or executing external actions. Even in a high-stakes engineering context, merely listing projects does not create direct risk of unintended consequences. The low severity reflects that information disclosure about project existence is less critical than write or destructive operations.
From the tool's definition Tool name 'list_projects' indicates a retrieval operation with no modification capability. The description is empty, but the name and context (sibling tools like create_plan, add_task, complete_task) suggest this retrieves or enumerates existing projects…
Attacks that exploit this kind of access
list_projects. It is categorised as a Read tool in the Keshro MCP MCP Server, which means it retrieves data without modifying state.
Register the Keshro MCP server in PolicyLayer and add a rule for list_projects: 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 Keshro MCP. Nothing to install.
list_projects 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_projects 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_projects. 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_projects is provided by the Keshro MCP server (jlewitt1/keshro-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 →