cursor_get_agent_requested_rules

Returns all Cursor rules that are agent-requested (no globs, not alwaysApply). These rules must be explicitly requested by agents by name.

Server Clodbridge rethunk-ai/clodbridge
Category Read
Risk class Low
Parameters 00 required

What cursor_get_agent_requested_rules does on Clodbridge

AI agents call cursor_get_agent_requested_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.

Why cursor_get_agent_requested_rules needs a policy

This tool retrieves configuration data (Cursor rules) from the .cursor directory without modifying, deleting, or executing anything. It is a pure read operation that queries rule metadata. The low severity reflects that accessing rule definitions poses minimal risk—the actual execution of those rules would be separate operations. No financial, destructive, or code execution capability is present.

From the tool's definition Tool description states it 'Returns all Cursor rules' - a retrieval operation with no modification or side effects. The verb 'Returns' and the passive nature of 'agent-requested' indicate data querying only.

Questions about cursor_get_agent_requested_rules

What does the cursor_get_agent_requested_rules tool do? +

Returns all Cursor rules that are agent-requested (no globs, not alwaysApply). These rules must be explicitly requested by agents by name. It is categorised as a Read tool in the Clodbridge MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on cursor_get_agent_requested_rules? +

Register the Clodbridge MCP server in PolicyLayer and add a rule for cursor_get_agent_requested_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.

What risk level is cursor_get_agent_requested_rules? +

cursor_get_agent_requested_rules is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit cursor_get_agent_requested_rules? +

Yes. Add a rate_limit block to the cursor_get_agent_requested_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.

How do I block cursor_get_agent_requested_rules completely? +

Set action: deny in the PolicyLayer policy for cursor_get_agent_requested_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.

What MCP server provides cursor_get_agent_requested_rules? +

cursor_get_agent_requested_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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.