Deploy Agent Skills as Cursor configuration.
AI agents use deploy_skills_to_cursor to create or update resources in MCP Project Orchestrator — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Project Orchestrator environment.
The tool deploys/writes configuration files for Cursor (an AI code editor). This is a Write operation as it creates or modifies configuration files. It does not appear to execute code or irreversibly destroy data, but misconfiguration could affect the development environment.
From the tool's definition Deploy Agent Skills as Cursor configuration
Documented attack patterns abuse exactly the kind of access deploy_skills_to_cursor gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Project Orchestrator, and nothing reaches the server without passing your rules. This is the rule we recommend for deploy_skills_to_cursor:
{
"version": "1",
"default": "deny",
"tools": {
"deploy_skills_to_cursor": {
"limits": [
{
"counter": "deploy_skills_to_cursor_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} deploy_skills_to_cursor stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Deploy Agent Skills as Cursor configuration. It is categorised as a Write tool in the MCP Project Orchestrator MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Project Orchestrator MCP server in PolicyLayer and add a rule for deploy_skills_to_cursor: 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 MCP Project Orchestrator. Nothing to install.
deploy_skills_to_cursor is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the deploy_skills_to_cursor 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 deploy_skills_to_cursor. 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.
deploy_skills_to_cursor is provided by the MCP Project Orchestrator MCP server (sparesparrow/mcp-project-orchestrator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Project Orchestrator, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
15 MCP Project Orchestrator tools catalogued and risk-classified — across an index of 43,000+ MCP servers.