list_tasks_tool
AI agents call list_tasks_tool to retrieve information from Capsulecrm without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list_*' naming convention consistently indicates retrieval without modification. No description provided, but contextual evidence from sibling tools and server description strongly suggests this retrieves a collection of tasks from CapsuleCRM without side effects. Confidence is slightly reduced due to empty tool description, but naming and context provide sufficient clarity to classify as Read with low severity.
From the tool's definition Tool name 'list_tasks_tool' indicates a listing operation. Sibling tools include 'find_tasks_tool' and 'get_task_tool', establishing a pattern where list/find/get operations are read-only.
Attacks that exploit this kind of access
list_tasks_tool. It is categorised as a Read tool in the Capsulecrm MCP Server, which means it retrieves data without modifying state.
Register the Capsulecrm MCP server in PolicyLayer and add a rule for list_tasks_tool: 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 Capsulecrm. Nothing to install.
list_tasks_tool 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 list_tasks_tool 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 list_tasks_tool. 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.
list_tasks_tool is provided by the Capsulecrm MCP server (monadsag/capsulecrm-mcp). 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 →