List all Codecks projects with their IDs. Use this to find a project ID for configuration.
AI agents call codecks_list_projects to retrieve information from Codecks MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing project data. It has no side effects, creates no resources, and cannot modify or delete anything. It is a simple listing/enumeration operation, which is the definition of a Read category tool.
From the tool's definition Tool name 'codecks_list_projects' and description 'List all Codecks projects with their IDs' indicate a read-only query operation that retrieves project information without modifying, deleting, or executing any side effects.
Attacks that exploit this kind of access
List all Codecks projects with their IDs. Use this to find a project ID for configuration. It is categorised as a Read tool in the Codecks MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Codecks MCP Server MCP server in PolicyLayer and add a rule for codecks_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 Codecks MCP Server. Nothing to install.
codecks_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 codecks_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 codecks_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.
codecks_list_projects is provided by the Codecks MCP Server MCP server (microkorg/codecks-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 →