Returns the full content of a named Cursor skill.
AI agents call cursor_get_skill 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 tool retrieves and queries skill definitions from the .cursor directory without modifying, deleting, or executing anything. It is purely informational—reading skill content to understand project-specific configurations. The blast radius of misuse is minimal; an agent could at worst read skill definitions it shouldn't have access to, but cannot modify or delete them.
From the tool's definition Tool description states it 'Returns the full content of a named Cursor skill', which is a retrieval operation with no side effects. The verb 'Returns' and the read-only nature of retrieving skill definitions aligns with the Read category.
Attacks that exploit this kind of access
Returns the full content of a named Cursor skill. 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_get_skill: 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_get_skill 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_get_skill 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_get_skill. 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_get_skill 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 →