Gets the current state of your OmniFocus database
AI agents call dump_database to retrieve information from OmniFocus MCP Enhanced 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 data from the OmniFocus database without modifying it. While dumping an entire database could expose sensitive task/project information and context (medium severity due to potential information disclosure), the core operation is read-only retrieval. It poses no financial risk, executes no code, and makes no irreversible changes.
From the tool's definition Tool description states 'Gets the current state of your OmniFocus database' with no modification, deletion, or execution indicated. The verb 'Gets' and 'dump' (in data context) indicate read-only retrieval of state information.
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 Enhanced, 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 Enhanced MCP Server, which means it retrieves data without modifying state.
Register the OmniFocus MCP Enhanced 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 Enhanced. 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 Enhanced MCP server (jqlts1/omnifocus-mcp-enhanced). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OmniFocus MCP Enhanced, 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.
18 OmniFocus MCP Enhanced tools catalogued and risk-classified — across an index of 43,000+ MCP servers.