Get all tasks for a specific Worksection project. Args: - id_project (string, required): Project ID - filter (string, optional): Set to
AI agents call worksection_get_tasks to retrieve information from Worksection MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves task data from a project without creating, modifying, deleting, or executing any operations. It is a straightforward read operation on project management data with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name contains 'get' and description states 'Get all tasks for a specific Worksection project' - a retrieval operation with no data modification or side effects.
Attacks that exploit this kind of access
Get all tasks for a specific Worksection project. Args: - id_project (string, required): Project ID - filter (string, optional): Set to. It is categorised as a Read tool in the Worksection MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Worksection MCP Server MCP server in PolicyLayer and add a rule for worksection_get_tasks: 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 Worksection MCP Server. Nothing to install.
worksection_get_tasks 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 worksection_get_tasks 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 worksection_get_tasks. 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.
worksection_get_tasks is provided by the Worksection MCP Server MCP server (novgorodskii/worksection-mcp-server). 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 →