AI agents call dump_database to retrieve information from OmniFocus-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves data from OmniFocus without modifying it, making it a Read operation. However, the severity is high because the database dump likely contains sensitive personal information including all tasks, projects, tags, metadata, and potentially private notes about the user's goals, work, and personal life.
From the tool's definition dump_database gets the current state of your OmniFocus database
Documented attack patterns abuse exactly the kind of access dump_database gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OmniFocus-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for dump_database:
{
"version": "1",
"default": "deny",
"tools": {
"dump_database": {}
}
} dump_database 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.
Gets the current state of your OmniFocus database. It is categorised as a Read tool in the OmniFocus-MCP MCP Server, which means it retrieves data without modifying state.
Register the 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 OmniFocus-MCP. 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 OmniFocus- MCP server (themotionmachine/omnifocus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 OmniFocus-MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
12 OmniFocus-MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.