AI agents call get_tasks to retrieve information from brainMD without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and aggregates existing task data across the vault without creating, modifying, or deleting any information. It is a read-only operation comparable to list or get operations. The blast radius of misuse is minimal—an AI agent could retrieve task data but cannot cause irreversible harm, financial loss, or system damage. Low severity is appropriate for information retrieval tools.
From the tool's definition Tool name is 'get_tasks' and description states 'Aggregate tasks vault-wide' — a query/retrieval operation with no modification capability.
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 brainMD, 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.
Aggregate tasks vault-wide. It is categorised as a Read tool in the brainMD MCP Server, which means it retrieves data without modifying state.
Register the brainMD 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 brainMD. 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 brainMD MCP server (mi4uu/brain.md). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from brainMD, 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.
17 brainMD tools catalogued and risk-classified — across an index of 43,000+ MCP servers.