AI agents call list_projects to retrieve information from Run402 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a list of projects scoped to the authenticated agent's organizational membership. It is a read-only query operation that returns data without creating, modifying, or deleting anything. The membership-scoping provides appropriate isolation. Severity is low because the blast radius of misuse is limited to unauthorized visibility of project metadata within authorized organizations.
From the tool's definition Tool name 'list_projects' and description 'List projects from the named, domain-aware inventory (GET /projects/v1)' indicates a query operation. Uses HTTP GET verb and explicitly performs 'List' action with no mention of modifications or side effects.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List projects from the named, domain-aware inventory (GET /projects/v1). Membership-scoped by default: every project owned by an org the agent. It is categorised as a Read tool in the Run402 MCP Server, which means it retrieves data without modifying state.
Register the Run402 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 Run402. 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 Run402 MCP server (kychee-com/run402). 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 →