AI agents call get_backlog to retrieve information from Zakar without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
get_backlog performs data retrieval and filtering operations only. It queries a backlog/task list with optional domain filtering, returning information without side effects. This is a classic Read operation—equivalent to 'list' or 'get'. There is no indication of data modification, deletion, code execution, or financial transactions.
From the tool's definition The tool 'list[s] open work' and retrieves 'curated tasks' and 'unresolved raw action items' from stored memories.
Attacks that exploit this kind of access
List open work, optionally scoped to one domain: curated tasks (open_brain_tasks) plus unresolved raw action items auto-extracted from memories. Domain scoping follows memory → project → domain. It is categorised as a Read tool in the Zakar MCP Server, which means it retrieves data without modifying state.
Register the Zakar MCP server in PolicyLayer and add a rule for get_backlog: 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 Zakar. Nothing to install.
get_backlog 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_backlog 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_backlog. 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_backlog is provided by the Zakar MCP server (tkbrannon/zakar). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_backlog is one line of Zakar's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →