AI agents call get_tasks to retrieve information from Habitca without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries task data from Habitica without creating, modifying, or deleting any data. It is a straightforward read operation that poses minimal security risk even if misused by an AI agent.
From the tool's definition Tool name 'get_tasks' and description 'List tasks. Optionally filter by type' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List tasks. Optionally filter by type. It is categorised as a Read tool in the Habitca MCP Server, which means it retrieves data without modifying state.
Register the Habitca 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 Habitca. 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 Habitca MCP server (leon-jarvis1/habitca_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 →