Schedule an important meeting during everyone
AI agents use schedule_meeting_during_lunch to create or update resources in Hilanet MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hilanet MCP environment.
This tool creates a new meeting entry, which is a reversible write operation (meetings can be cancelled or rescheduled). While satirical in nature (scheduling during lunch is inconvenient rather than malicious), it modifies organizational data rather than executing arbitrary operations or causing destructive damage.
From the tool's definition schedule_meeting_during_lunch: creates and modifies calendar/meeting data; 'Schedule an important meeting' indicates a write operation that creates a new calendar entry
Documented attack patterns abuse exactly the kind of access schedule_meeting_during_lunch gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Hilanet MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for schedule_meeting_during_lunch:
{
"version": "1",
"default": "deny",
"tools": {
"schedule_meeting_during_lunch": {
"limits": [
{
"counter": "schedule_meeting_during_lunch_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}schedule_meeting_during_lunch stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Schedule an important meeting during everyone. It is categorised as a Write tool in the Hilanet MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hilanet MCP server in PolicyLayer and add a rule for schedule_meeting_during_lunch: 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 Hilanet MCP. Nothing to install.
schedule_meeting_during_lunch 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 schedule_meeting_during_lunch 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 schedule_meeting_during_lunch. 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.
schedule_meeting_during_lunch is provided by the Hilanet MCP server (adird/hilanet-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 Hilanet MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
12 Hilanet MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.