configure_offline_sync
Configure which tables/records are available offline in mobile. [Write]
This record as markdown: /tools/servicenow-mcp-server/configure-offline-sync.md
What configure_offline_sync does on ServiceNow MCP Server
AI agents use configure_offline_sync 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.
Why configure_offline_sync is rated Medium
This tool creates or modifies configuration settings for offline data synchronization in mobile contexts. While reversible (configurations can be reconfigured), it affects critical data accessibility and sync behavior. The high severity reflects potential for misuse: an AI agent could disable access to essential tables, corrupt sync state, or expose sensitive data by incorrectly configuring offline availability.
From the tool's definition Tool name "configure_offline_sync" and description explicitly states it "Configure which tables/records are available offline in mobile" — this modifies system configuration that determines data availability and synchronization behavior.
Attacks that exploit this kind of access
The rule that runs configure_offline_sync 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 configure_offline_sync, this is the rule to start with:
configure_offline_sync 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 ServiceNow MCP Server, apply this rule, and every configure_offline_sync call is checked against it from then on.
Questions about configure_offline_sync
Configure which tables/records are available offline in mobile. [Write]. 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.
Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for configure_offline_sync: 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.
configure_offline_sync 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 configure_offline_sync 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 configure_offline_sync. 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.
configure_offline_sync 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.
More on ServiceNow MCP Server, and thousands of servers like it.
This server
Across the catalogue