upload_attachment

Upload a base64-encoded attachment to a ServiceNow record (requires WRITE_ENABLED=true).

SERVERServiceNow-MCP SOURCEtedorigawa001/servicenow-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/tedorigawa001-servicenow-mcp/upload-attachment.md

WHAT IT DOES

What upload_attachment does on ServiceNow-MCP

AI agents use upload_attachment 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.

RISK

Why upload_attachment is rated Medium

This tool creates new attachment records within ServiceNow, modifying the state of existing records by adding file attachments. While it changes data, the operation is reversible (attachments can be deleted), making it a Write operation rather than Destructive.

From the tool's definition Tool description states 'Upload a base64-encoded attachment to a ServiceNow record' and explicitly requires 'WRITE_ENABLED=true', indicating it creates/adds data to ServiceNow records.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs upload_attachment safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceNow-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For upload_attachment, this is the rule to start with:

upload_attachment Rate-limited

upload_attachment 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": {
    "upload_attachment": {
      "limits": [
        {
          "counter": "upload_attachment_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ServiceNow-MCP, apply this rule, and every upload_attachment call is checked against it from then on.

FAQ

Questions about upload_attachment

What does the upload_attachment tool do? +

Upload a base64-encoded attachment to a ServiceNow record (requires WRITE_ENABLED=true). 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.

How do I enforce a policy on upload_attachment? +

Register the ServiceNow MCP server in PolicyLayer and add a rule for upload_attachment: 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.

What risk level is upload_attachment? +

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

Can I rate-limit upload_attachment? +

Yes. Add a rate_limit block to the upload_attachment 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 upload_attachment completely? +

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

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

KEEP EXPLORING

More on ServiceNow, and thousands of servers like it.

This server

All 495 ServiceNow tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →