Get workflow context details
AI agents call workflow_context_get to retrieve information from ServiceNow MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves workflow context information from ServiceNow ITSM systems. It performs a query operation with no side effects—it does not create, modify, delete, or execute actions. The worst-case misuse would be unauthorized information disclosure of workflow details, which poses a low blast radius compared to tools that modify incidents, approve changes, or execute scripts.
From the tool's definition Tool name 'workflow_context_get' and description 'Get workflow context details' indicate retrieval of workflow state/metadata without modification. The 'get' verb and lack of any write/execute/delete language confirm read-only behavior.
Attacks that exploit this kind of access
Get workflow context details. It is categorised as a Read tool in the ServiceNow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for workflow_context_get: 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.
workflow_context_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the workflow_context_get 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 workflow_context_get. 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.
workflow_context_get is provided by the ServiceNow MCP Server MCP server (schwarztim/servicenow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →