AI agents invoke switch_perspective to trigger actions in OmniFocus MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers a UI/navigation action in OmniFocus — switching the active perspective in the front window. It doesn't read, write, or delete data, but it executes an interface operation that changes application state. The blast radius is low since it only affects the view/navigation state of the app.
From the tool's definition Switch front window to a perspective
Documented attack patterns abuse exactly the kind of access switch_perspective gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OmniFocus MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for switch_perspective:
{
"version": "1",
"default": "deny",
"tools": {
"switch_perspective": {
"limits": [
{
"counter": "switch_perspective_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}switch_perspective stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Switch front window to a perspective. It is categorised as a Execute tool in the OmniFocus MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the OmniFocus MCP Server MCP server in PolicyLayer and add a rule for switch_perspective: 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 Server. Nothing to install.
switch_perspective is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the switch_perspective 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 switch_perspective. 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.
switch_perspective is provided by the OmniFocus MCP Server MCP server (s-morgan-jeffries/omnifocus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OmniFocus MCP Server, 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.
21 OmniFocus MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.