list_omnifocus_folders
Lists folders in OmniFocus. Folders group related projects (e.g. "Work", "Personal"). Use list_omnifocus_projects to see the projects inside them.
This record as markdown: /tools/com-local-mcp-local-mcp/list-omnifocus-folders.md
What list_omnifocus_folders does on Local
AI agents call list_omnifocus_folders to retrieve information from Local without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — |
Parameters from the server's own tool schema.
Why list_omnifocus_folders is rated Low
This tool only retrieves and queries folder structure from OmniFocus without making any changes to data. It has no side effects, cannot delete or modify folders/projects, and presents minimal risk if misused by an AI agent. The information exposed (folder names like 'Work', 'Personal') is organizational metadata with low sensitivity.
From the tool's definition Tool name contains 'list_' and description states 'Lists folders in OmniFocus', indicating a retrieval operation with no modification capability. The reference to sibling tool 'list_omnifocus_projects' further confirms this is a Read operation.
Attacks that exploit this kind of access
The rule that runs list_omnifocus_folders safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_omnifocus_folders, this is the rule to start with:
list_omnifocus_folders is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every list_omnifocus_folders call is checked against it from then on.
Questions about list_omnifocus_folders
Lists folders in OmniFocus. Folders group related projects (e.g. "Work", "Personal"). Use list_omnifocus_projects to see the projects inside them. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
list_omnifocus_folders accepts 1 parameter: limit. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for list_omnifocus_folders: 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 Local. Nothing to install.
list_omnifocus_folders 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 list_omnifocus_folders 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 list_omnifocus_folders. 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.
list_omnifocus_folders is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue