[Write] Schedule a Change Advisory Board (CAB) meeting
AI agents use schedule_cab_meeting to create or update resources in ServiceNow-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ServiceNow-MCP environment.
Scheduling a CAB meeting creates a new record in ServiceNow's system that affects downstream change management processes. This is a reversible write operation (meetings can be rescheduled or cancelled), not a read-only query, nor an immediate destructive action. However, it has organizational impact since CAB meetings drive change approval workflows.
From the tool's definition Tool name 'schedule_cab_meeting' and description '[Write] Schedule a Change Advisory Board (CAB) meeting' indicate creation of a meeting record/calendar entry in ServiceNow.
Attacks that exploit this kind of access
[Write] Schedule a Change Advisory Board (CAB) meeting. It is categorised as a Write tool in the ServiceNow-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ServiceNow- MCP server in PolicyLayer and add a rule for schedule_cab_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 ServiceNow-MCP. Nothing to install.
schedule_cab_meeting 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_cab_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.
Set action: deny in the PolicyLayer policy for schedule_cab_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.
schedule_cab_meeting is provided by the ServiceNow- MCP server (tedorigawa001/servicenow-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 →