get_tasks

THE RISK

Low Risk

Why get_tasks needs a policy

This tool performs a straightforward data retrieval operation (listing/querying tasks), which is characteristic of the Read category. There is no indication of data modification, deletion, code execution, or financial impact. The low severity reflects that listing tasks poses minimal risk even if accessed by an unauthorized agent, as it only exposes information rather than enabling changes to system state.

From the tool's definition Tool name is 'get_tasks' and description states 'List tasks in a project' - a retrieval operation with no modification or side effects.

Documented attack patterns abuse exactly the kind of access get_tasks gives an agent:

POLICY

How to control get_tasks

PolicyLayer is an MCP gateway — it sits between your AI agents and Writbase, 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.

Create a free account and register Writbase — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Writbase tools

Write add_task Create a new task. ${departmentRequired ? Write assign_task Create a task in a department where you have assign permission. Use this to create work in Write manage_agent_keys List, create, update, deactivate, or rotate agent keys. Manager only. Write manage_agent_permissions Grant, revoke, or list permissions for an agent key. Manager only. Write manage_departments Create, rename, or archive departments. Manager only. Write manage_projects Create, rename, or archive projects. Manager only. Write subscribe Register or manage webhook subscriptions for task event notifications. Write update_task Update an existing task. Pass the version from get_tasks to detect conflicts.${noProjectsN

All 13 Writbase tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_tasks

What does the get_tasks tool do? +

List tasks in a project.${noProjectsNote}. It is categorised as a Read tool in the Writbase MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_tasks? +

Register the Writbase 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 Writbase. 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 Writbase MCP server (https://{PROJECT_REF}.supabase.co/functions/v1/mcp-server/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Writbase tool call.

Start from Writbase, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →