Closes the task. Use this tool only if the user ask you to close the task. DO NOT use this tool until the user confirms the task is complete.
AI agents use close_task to create or update resources in Webvizio MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Webvizio MCP Server environment.
An AI agent can call close_task faster than any human can review — one bad instruction and it creates or modifies resources in Webvizio MCP Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Closes the task. Use this tool only if the user ask you to close the task. DO NOT use this tool until the user confirms the task is complete. It is categorised as a Write tool in the Webvizio MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Webvizio MCP Server MCP server in PolicyLayer and add a rule for close_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 Webvizio MCP Server. Nothing to install.
close_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 close_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 close_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.
close_task is provided by the Webvizio MCP Server MCP server (webvizio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.