Gets the current state of your OmniFocus database. Prefer query_omnifocus or filter_tasks for targeted lookups.
AI agents call dump_database to retrieve information from Codex Omnifocus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and exports the entire OmniFocus database state without modification. While it's Read category (no side effects), severity is raised to medium rather than low because: (1) dumping an entire database exposes all task data, projects, tags, and metadata in aggregate—higher blast radius than targeted queries; (2) an agent could inadvertently exfiltrate sensitive personal/professional information; (3)…
From the tool's definition Tool name 'dump_database' and description 'Gets the current state of your OmniFocus database' indicates a retrieval operation.
Attacks that exploit this kind of access
Gets the current state of your OmniFocus database. Prefer query_omnifocus or filter_tasks for targeted lookups. It is categorised as a Read tool in the Codex Omnifocus MCP Server, which means it retrieves data without modifying state.
Register the Codex Omnifocus MCP server in PolicyLayer and add a rule for dump_database: 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 Codex Omnifocus. Nothing to install.
dump_database 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 dump_database 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 dump_database. 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.
dump_database is provided by the Codex Omnifocus MCP server (phd-peter/codex-omnifocus-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 →