complete_task
Mark a task as complete (requires WRITE_ENABLED=true)
This record as markdown: /tools/tedorigawa001-servicenow-mcp/complete-task.md
What complete_task does on ServiceNow-MCP
AI agents use complete_task 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.
Why complete_task is rated Medium
This tool creates or modifies data reversibly by changing task status to complete. It does not delete data, execute arbitrary code, move money, or trigger destructive actions. While it affects workflow state in an enterprise system, the change is not permanent or irreversible. Classified as Write rather than Execute because it performs a specific, bounded state transition rather than executing arbitrary logic.
From the tool's definition Tool description states 'Mark a task as complete' which modifies task status in ServiceNow. The requirement flag 'WRITE_ENABLED=true' confirms this is a write operation. Task completion is a reversible state change (tasks can be reopened).
Attacks that exploit this kind of access
The rule that runs complete_task 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 complete_task, this is the rule to start with:
complete_task 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, apply this rule, and every complete_task call is checked against it from then on.
Questions about complete_task
Mark a task as complete (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.
Register the ServiceNow MCP server in PolicyLayer and add a rule for complete_task: 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.
complete_task 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 complete_task 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 complete_task. 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.
complete_task 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.
More on ServiceNow, and thousands of servers like it.
This server
Across the catalogue