Get the items visible in a specific OmniFocus perspective. Shows what tasks and projects are displayed when viewing that perspective
AI agents call get_perspective_view 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 queries and returns task/project information from an OmniFocus perspective. It has no side effects, does not modify data, and does not execute operations. The blast radius of misuse is minimal—an agent could only view existing tasks, not alter them. This is a standard Read operation typical of task management query tools.
From the tool's definition Tool description states 'Get the items visible' and 'Shows what tasks and projects are displayed' — purely retrieves and displays data without modification.
Documented attack patterns abuse exactly the kind of access get_perspective_view 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 get_perspective_view:
{
"version": "1",
"default": "deny",
"tools": {
"get_perspective_view": {}
}
}get_perspective_view 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.
Get the items visible in a specific OmniFocus perspective. Shows what tasks and projects are displayed when viewing that perspective. 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 get_perspective_view: 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.
get_perspective_view 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_perspective_view 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_perspective_view. 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_perspective_view 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.