Low Risk

get_tasks

Get tasks filtered by status, tags, or deadline.

How to control get_tasks ↓

AI agents call get_tasks to retrieve information from Compass MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves and queries task data based on filter criteria (status, tags, deadline). It performs no side effects, does not modify state, and does not execute code or trigger external operations. It is a straightforward read operation that queries local markdown-based task storage.

From the tool's definition Tool name 'get_tasks' and description 'Get tasks filtered by status, tags, or deadline' indicate a retrieval operation with no modification or execution of external operations.

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 Compass MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_tasks:

policy.json
{
  "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.

  1. Create a free account and register Compass MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_tasks tool do? +

Get tasks filtered by status, tags, or deadline. It is categorised as a Read tool in the Compass MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_tasks? +

Register the Compass 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 Compass MCP. Nothing to install.

What risk level is get_tasks? +

get_tasks is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_tasks? +

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.

How do I block get_tasks completely? +

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.

What MCP server provides get_tasks? +

get_tasks is provided by the Compass MCP server (richlira/compass-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Compass MCP tool call.

Deterministic rules across all 6 Compass MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

6 Compass MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.