connect_servicenow
Connect to your ServiceNow instance using your username and password. Credentials are stored locally and never sent to Claude's servers.
This record as markdown: /tools/com-local-mcp-local-mcp/connect-servicenow.md
What connect_servicenow does on Local
AI agents use connect_servicenow 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 |
|---|---|---|---|
instance | string | Yes | Your ServiceNow instance hostname, e.g. 'mycompany.service-now.com' or just 'mycompany' |
password | string | Yes | Your ServiceNow password |
username | string | Yes | Your ServiceNow username |
Parameters from the server's own tool schema.
Why connect_servicenow is rated Medium
This tool stores credentials locally to establish a connection to a ServiceNow instance. Storing credentials is a Write operation (persisting data to local storage). It is not purely Read since it creates/saves authentication state. The severity is medium because misuse could expose ServiceNow credentials or establish unauthorized access to a ServiceNow instance, though the description claims credentials stay local.
From the tool's definition 'Connect to your ServiceNow instance using your username and password. Credentials are stored locally'
Risk signalsHandles credentials or secrets (password)
Attacks that exploit this kind of access
The rule that runs connect_servicenow 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 connect_servicenow, this is the rule to start with:
connect_servicenow 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 connect_servicenow call is checked against it from then on.
Questions about connect_servicenow
Connect to your ServiceNow instance using your username and password. Credentials are stored locally and never sent to Claude's servers. 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.
connect_servicenow accepts 3 parameters: instance, password, username. Required: instance, password, username. 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 connect_servicenow: 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.
connect_servicenow 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 connect_servicenow 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 connect_servicenow. 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.
connect_servicenow 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