Add a new schedule item to the Schedule sheet
AI agents use add_schedule to create or update resources in Wedding Planner MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wedding Planner MCP Server environment.
This tool creates new schedule entries in the wedding planner's sheet, modifying the document irreversibly in practice but not destructively. The risk is medium because misuse could clutter or corrupt a wedding planning schedule (affecting event coordination), but the impact is reversible by deletion.
From the tool's definition Tool description states 'Add a new schedule item to the Schedule sheet' — this creates new data in a Google Sheets document. The verb 'Add' and context of writing to a sheet indicate data creation.
Attacks that exploit this kind of access
Add a new schedule item to the Schedule sheet. It is categorised as a Write tool in the Wedding Planner MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Wedding Planner MCP Server MCP server in PolicyLayer and add a rule for add_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 Wedding Planner MCP Server. Nothing to install.
add_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 add_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 add_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.
add_schedule is provided by the Wedding Planner MCP Server MCP server (kiboud/weddingplanner_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 →