create_daily_plan
AI agents use create_daily_plan to create or update resources in Super Productivity MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Super Productivity MCP environment.
Creates or modifies data (a daily plan) reversibly within the productivity system. No destructive deletion, financial transactions, or arbitrary code execution. Severity is low because plans are not business-critical system data and can be edited or deleted. Confidence reduced to 0.7 due to empty description, though naming conventions of sibling Create tools provide reasonable context.
From the tool's definition Tool name 'create_daily_plan' and context of Super Productivity task management system indicate creation of a new plan/task artifact.
Attacks that exploit this kind of access
create_daily_plan. It is categorised as a Write tool in the Super Productivity MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Super Productivity MCP server in PolicyLayer and add a rule for create_daily_plan: 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 Super Productivity MCP. Nothing to install.
create_daily_plan is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_daily_plan 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 create_daily_plan. 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.
create_daily_plan is provided by the Super Productivity MCP server (rochadelon/super-productivity-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →