AI agents call filter_activities to retrieve information from Twenty MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Filtering is a read-only operation that retrieves a subset of existing data based on search parameters. It has no side effects, does not create, modify, delete, or execute external actions. The tool belongs in the Read category with low severity since it only retrieves data without risk of data loss or unintended modifications.
From the tool's definition Tool name 'filter_activities' and description 'Filter activities by specific criteria' indicate a querying/filtering operation with no modification capability.
Documented attack patterns abuse exactly the kind of access filter_activities 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 filter_activities:
{
"version": "1",
"default": "deny",
"tools": {
"filter_activities": {}
}
}filter_activities is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Filter activities by specific criteria. It is categorised as a Read tool in the Twenty MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Twenty MCP Server MCP server in PolicyLayer and add a rule for filter_activities: 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.
filter_activities is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the filter_activities 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 filter_activities. 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.
filter_activities is provided by the Twenty MCP Server MCP server (jezweb/twenty-mcp). 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.
29 Twenty MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.