List projects visible to the configured API token, optionally filtered by workspace.
AI agents call staticx_list_projects to retrieve information from StaticX MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
staticx_list_projects performs a query/retrieval of existing projects without creating, modifying, deleting, or executing any operations. It is a read-only listing function with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name contains 'list' and description states it 'List projects visible to the configured API token' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
List projects visible to the configured API token, optionally filtered by workspace. It is categorised as a Read tool in the StaticX MCP Server MCP Server, which means it retrieves data without modifying state.
Register the StaticX MCP Server MCP server in PolicyLayer and add a rule for staticx_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 StaticX MCP Server. Nothing to install.
staticx_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 staticx_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 staticx_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.
staticx_list_projects is provided by the StaticX MCP Server MCP server (madprodworks-coder/staticx-mcp-server). 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 →