AI agents use create_shift to create or update resources in Mcp Sling — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Sling environment.
This tool creates new workforce scheduling data (shifts) but does not permanently destroy data, execute arbitrary code, or move money. The impact is limited to adding a new record in a scheduling system, which is a typical write operation. Severity is medium because misuse could disrupt workforce scheduling and operational planning, but the effects are recoverable through standard administrative actions.
From the tool's definition Tool name is 'create_shift' and description states 'Create a new shift for a user'. The verb 'create' and action of generating a new scheduled work period indicate data creation, which is reversible (shifts can be modified or deleted by administrators).
Attacks that exploit this kind of access
Create a new shift for a user. Shifts represent scheduled work periods. It is categorised as a Write tool in the Mcp Sling MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Sling MCP server in PolicyLayer and add a rule for create_shift: 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 Sling. Nothing to install.
create_shift 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_shift 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_shift. 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_shift is provided by the Mcp Sling MCP server (poncheck/mcp-sling). 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 →