schedule_meeting · HR Assistant Agent MCP: Risk & Policy

WHAT IT DOES

What schedule_meeting does on HR Assistant Agent

AI agents use schedule_meeting to create or update resources in HR Assistant Agent — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your HR Assistant Agent environment.

WHY IT NEEDS A POLICY

Why schedule_meeting needs a policy

This tool creates a new meeting record in the system, modifying the organizational calendar state. It is reversible (meetings can be cancelled via cancel_meeting), so it qualifies as Write rather than Destructive.

From the tool's definition The tool name 'schedule_meeting' and description 'Schedule a meeting for an employee' indicate it creates a new calendar entry, which is a data creation operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

schedule_meeting Rate-limited

schedule_meeting 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "schedule_meeting": {
      "limits": [
        {
          "counter": "schedule_meeting_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches HR Assistant Agent, so you can run agents against it safely.

FAQ

Questions about schedule_meeting

What does the schedule_meeting tool do? +

Schedule a meeting for an employee. It is categorised as a Write tool in the HR Assistant Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on schedule_meeting? +

Register the HR Assistant Agent MCP server in PolicyLayer and add a rule for schedule_meeting: 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 HR Assistant Agent. Nothing to install.

What risk level is schedule_meeting? +

schedule_meeting is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit schedule_meeting? +

Yes. Add a rate_limit block to the schedule_meeting 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.

How do I block schedule_meeting completely? +

Set action: deny in the PolicyLayer policy for schedule_meeting. 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.

What MCP server provides schedule_meeting? +

schedule_meeting is provided by the HR Assistant Agent MCP server (nishu8875/hr-assistant-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.