Propose an energy-aware daily schedule based on today's readiness score
AI agents use propose_schedule to create or update resources in Wellness Planner — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wellness Planner environment.
This tool creates a new schedule recommendation (Write category) rather than merely retrieving data (Read). However, it does not execute external actions, delete data, or involve financial transactions. The severity is low because proposing a schedule is reversible—users can ignore or modify recommendations without permanent consequences.
From the tool's definition Tool 'propose_schedule' generates and proposes a daily schedule based on readiness scores. The verb 'propose' indicates creation of a new schedule artifact.
Attacks that exploit this kind of access
Propose an energy-aware daily schedule based on today's readiness score. It is categorised as a Write tool in the Wellness Planner MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Wellness Planner MCP server in PolicyLayer and add a rule for propose_schedule: 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 Wellness Planner. Nothing to install.
propose_schedule 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 propose_schedule 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 propose_schedule. 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.
propose_schedule is provided by the Wellness Planner MCP server (rwking/wellness_planner). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
propose_schedule is one line of Wellness Planner's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →