AI agents use createOneViewFilter to create or update resources in Twenty MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Twenty MCP Server environment.
The 'createOne' prefix establishes this as a write operation that creates a new data entity (a view filter). This is reversible (the filter can be deleted or modified), so it does not qualify as Destructive. The impact is limited to adding a configuration object that affects data display/filtering in the CRM, with medium severity due to potential impact on other users' view configurations if misused.
From the tool's definition Tool name 'createOneViewFilter' and description 'Create One viewFilter' indicate a create operation that modifies CRM data by adding a new view filter configuration.
Documented attack patterns abuse exactly the kind of access createOneViewFilter gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Twenty MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for createOneViewFilter:
{
"version": "1",
"default": "deny",
"tools": {
"createOneViewFilter": {
"limits": [
{
"counter": "createoneviewfilter_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}createOneViewFilter 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 One viewFilter. It is categorised as a Write tool in the Twenty MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Twenty MCP Server MCP server in PolicyLayer and add a rule for createOneViewFilter: 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 Twenty MCP Server. Nothing to install.
createOneViewFilter 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 createOneViewFilter 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 createOneViewFilter. 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.
createOneViewFilter is provided by the Twenty MCP Server MCP server (jdu278/twenty-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Twenty MCP Server, 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.
219 Twenty MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.