Create a new worker set
AI agents use create_worker_set to create or update resources in Rockfish MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rockfish MCP Server environment.
Creating a worker set is a reversible write operation that adds configuration to the system. While it allocates computational resources, the action itself can be undone by deleting the worker set (delete_worker_set is available on this server). This is not destructive (not irreversible), not execute (not running external code), and not financial.
From the tool's definition Tool name 'create_worker_set' and description 'Create a new worker set' indicate a create operation that adds a new resource to the ML platform.
Attacks that exploit this kind of access
Create a new worker set. It is categorised as a Write tool in the Rockfish MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Rockfish MCP Server MCP server in PolicyLayer and add a rule for create_worker_set: 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 Rockfish MCP Server. Nothing to install.
create_worker_set 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 create_worker_set 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 create_worker_set. 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.
create_worker_set is provided by the Rockfish MCP Server MCP server (wolfdancer/rockfish-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 →