get_task
Get details of a specific task by ID
This record as markdown: /tools/denisalmeida-twenty-crm-mcp/get-task.md
What get_task does on Twenty CRM MCP Server
AI agents call get_task to retrieve information from Twenty CRM MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_task is rated Low
This tool retrieves task information by ID without modifying, creating, or deleting any data. It is a pure read operation consistent with query/fetch semantics in CRM systems. The low severity reflects minimal blast radius—an AI agent retrieving task details poses negligible security risk.
From the tool's definition Tool name 'get_task' and description 'Get details of a specific task by ID' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_task safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Twenty CRM MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_task, this is the rule to start with:
get_task is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Twenty CRM MCP Server, apply this rule, and every get_task call is checked against it from then on.
Questions about get_task
Get details of a specific task by ID. It is categorised as a Read tool in the Twenty CRM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Twenty CRM MCP Server MCP server in PolicyLayer and add a rule for get_task: 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 CRM MCP Server. Nothing to install.
get_task 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 get_task 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 get_task. 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.
get_task is provided by the Twenty CRM MCP Server MCP server (denisalmeida/twenty-crm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Twenty CRM MCP Server, and thousands of servers like it.
This server
Across the catalogue