copy_attachment

Copy an existing ServiceNow attachment onto another record, entirely server-side

SERVERServiceNow MCP Server SOURCE@aartiq/servicenow-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/servicenow-mcp-server/copy-attachment.md

WHAT IT DOES

What copy_attachment does on ServiceNow MCP Server

AI agents use copy_attachment to create or update resources in ServiceNow MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ServiceNow MCP Server environment.

RISK

Why copy_attachment is rated Medium

Creates new attachment data by copying existing files; reversible via deletion without destructive cascade.

From the tool's definition Copy attachment onto another record, entirely server-side

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs copy_attachment safely

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

copy_attachment Rate-limited

copy_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": {
    "copy_attachment": {
      "limits": [
        {
          "counter": "copy_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 Server, apply this rule, and every copy_attachment call is checked against it from then on.

FAQ

Questions about copy_attachment

What does the copy_attachment tool do? +

Copy an existing ServiceNow attachment onto another record, entirely server-side. It is categorised as a Write tool in the ServiceNow MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on copy_attachment? +

Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for copy_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 Server. Nothing to install.

What risk level is copy_attachment? +

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

Can I rate-limit copy_attachment? +

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

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

copy_attachment is provided by the ServiceNow MCP Server MCP server (@aartiq/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 MCP Server, and thousands of servers like it.

This server

All 504 ServiceNow MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

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