update_watchtower_finding
Update the triage status of one WatchTower waste finding: confirmed to accept the signal, dismissed to reject it, or new to reopen it. The resolved status is system-managed and cannot be written.
This record as markdown: /tools/sankahq-sanka-mcp/update-watchtower-finding.md
What update_watchtower_finding does on Sanka MCP Server
AI agents use update_watchtower_finding to create or update resources in Sanka MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sanka MCP Server environment.
Why update_watchtower_finding is rated Medium
This is a Write action because it modifies the state of existing records (WatchTower findings) in a reversible manner. The user can change a finding from confirmed to dismissed or reopen it to 'new', so the changes are not permanent.
From the tool's definition The tool updates triage status of findings with states: confirmed, dismissed, or new. The description explicitly states it performs status updates ('Update the triage status'), which is a reversible modification operation.
Attacks that exploit this kind of access
The rule that runs update_watchtower_finding safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sanka MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_watchtower_finding, this is the rule to start with:
update_watchtower_finding 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 Sanka MCP Server, apply this rule, and every update_watchtower_finding call is checked against it from then on.
Questions about update_watchtower_finding
Update the triage status of one WatchTower waste finding: confirmed to accept the signal, dismissed to reject it, or new to reopen it. The resolved status is system-managed and cannot be written. It is categorised as a Write tool in the Sanka MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for update_watchtower_finding: 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 Sanka MCP Server. Nothing to install.
update_watchtower_finding 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 update_watchtower_finding 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 update_watchtower_finding. 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.
update_watchtower_finding is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sanka MCP Server, and thousands of servers like it.
This server
Across the catalogue