Lists all available Cursor rules with their names, descriptions, and modes.
AI agents call cursor_list_rules to retrieve information from Clodbridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure retrieval operation that enumerates configuration metadata from the .cursor directory. It has no side effects, does not execute code, and does not modify any state. The blast radius of misuse is minimal—an attacker gains visibility into project rules but cannot directly abuse them through this tool alone.
From the tool's definition Tool name and description indicate it 'Lists all available Cursor rules with their names, descriptions, and modes' — a read-only operation that retrieves and queries data without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Lists all available Cursor rules with their names, descriptions, and modes. It is categorised as a Read tool in the Clodbridge MCP Server, which means it retrieves data without modifying state.
Register the Clodbridge MCP server in PolicyLayer and add a rule for cursor_list_rules: 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 Clodbridge. Nothing to install.
cursor_list_rules 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 cursor_list_rules 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 cursor_list_rules. 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.
cursor_list_rules is provided by the Clodbridge MCP server (rethunk-ai/clodbridge). 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 →