servicenow_add_comment
Add a comment or work note to a ServiceNow incident. Comments are visible to the caller; work notes are internal only.
This record as markdown: /tools/com-local-mcp-local-mcp/servicenow-add-comment.md
What servicenow_add_comment does on Local
AI agents use servicenow_add_comment to create or update resources in Local, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Local environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | string | Yes | Comment or work note text |
type | string | — | 'comment' (visible to caller, default) or 'work_note' (internal only) |
sys_id | string | Yes | Incident sys_id from servicenow_get_incident |
Parameters from the server's own tool schema.
Why servicenow_add_comment is rated Medium
This tool creates or modifies data (adds comments/work notes to incidents) but does not delete or irreversibly destroy information, nor does it execute arbitrary code or move financial assets.
From the tool's definition Tool description states 'Add a comment or work note to a ServiceNow incident', which modifies incident data by appending comments or internal notes. This is a reversible write operation.
Attacks that exploit this kind of access
The rule that runs servicenow_add_comment safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For servicenow_add_comment, this is the rule to start with:
servicenow_add_comment 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every servicenow_add_comment call is checked against it from then on.
Questions about servicenow_add_comment
Add a comment or work note to a ServiceNow incident. Comments are visible to the caller; work notes are internal only. It is categorised as a Write tool in the Local MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
servicenow_add_comment accepts 3 parameters: text, type, sys_id. Required: text, sys_id. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for servicenow_add_comment: 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 Local. Nothing to install.
servicenow_add_comment 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 servicenow_add_comment 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 servicenow_add_comment. 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.
servicenow_add_comment is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue