AI agents call get_tasks to retrieve information from SP-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves task information from the Super Productivity app without creating, modifying, deleting, or executing any operations. It is a straightforward data query operation with no capability to alter application state or trigger external actions. The blast radius of misuse is minimal—an AI agent could only retrieve existing task data, which poses low risk.
From the tool's definition Tool name 'get_tasks' and description 'Get all tasks from Super Productivity' indicate data retrieval with no modification. The verb 'Get' denotes a read operation that queries existing task data without side effects.
Documented attack patterns abuse exactly the kind of access get_tasks gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SP-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_tasks:
{
"version": "1",
"default": "deny",
"tools": {
"get_tasks": {}
}
}get_tasks 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.
Get all tasks from Super Productivity. It is categorised as a Read tool in the SP-MCP MCP Server, which means it retrieves data without modifying state.
Register the SP- MCP server in PolicyLayer and add a rule for 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 SP-MCP. Nothing to install.
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 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 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.
get_tasks is provided by the SP- MCP server (organicmoron/sp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 SP-MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
10 SP-MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.