AI agents use create_sift to create or update resources in Sifter — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sifter environment.
This tool creates new data structures (sifts) within the system. Creation is reversible via the delete_sift sibling tool, making this a Write rather than Destructive action. Severity is medium because misuse could create numerous unwanted records or pollute the document store, but the impact is limited to the sifter application scope and is reversible.
From the tool's definition Tool name 'create_sift' indicates creation of a new sift (schema-defined record structure). Sibling tool 'delete_sift' confirms that sifts are persistent entities that can be created and destroyed.
Documented attack patterns abuse exactly the kind of access create_sift gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sifter, and nothing reaches the server without passing your rules. This is the rule we recommend for create_sift:
{
"version": "1",
"default": "deny",
"tools": {
"create_sift": {
"limits": [
{
"counter": "create_sift_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_sift 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.
create_sift. It is categorised as a Write tool in the Sifter MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sifter MCP server in PolicyLayer and add a rule for create_sift: 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 Sifter. Nothing to install.
create_sift 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_sift 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_sift. 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_sift is provided by the Sifter MCP server (sifter-ai/sifter). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 Sifter tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
15 Sifter tools catalogued and risk-classified — across an index of 42,500+ MCP servers.