Get top actionable tasks by priority (excludes done/cancelled/failed/blocked unless status filter is set).${noProjectsNote}
AI agents call get_top_tasks to retrieve information from Writbase without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a query/retrieval operation that returns filtered task data without side effects. It does not create, modify, delete, or execute any actions. The severity is low because unauthorized access to task metadata poses minimal risk compared to other tool categories, though information disclosure could be a concern in sensitive environments.
From the tool's definition Tool retrieves tasks filtered by priority and status; described as 'Get top actionable tasks' with no mention of creating, modifying, deleting, or executing operations. Returns data only.
Documented attack patterns abuse exactly the kind of access get_top_tasks gives an agent:
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_top_tasks:
{
"version": "1",
"default": "deny",
"tools": {
"get_top_tasks": {}
}
}get_top_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 top actionable tasks by priority (excludes done/cancelled/failed/blocked unless status filter is set).${noProjectsNote}. It is categorised as a Read tool in the Writbase MCP Server, which means it retrieves data without modifying state.
Register the Writbase MCP server in PolicyLayer and add a rule for get_top_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.
get_top_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_top_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_top_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_top_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.
Start from Writbase, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 Writbase tools catalogued and risk-classified — across an index of 43,000+ MCP servers.