list_watchtower_findings
List WatchTower waste findings (upcoming renewals, vendor price creep, possibly duplicate vendors) in the authenticated workspace, with optional status and finding_type filters. Findings with buy_request_id already link to a Sanka Buy request.
This record as markdown: /tools/sankahq-sanka-mcp/list-watchtower-findings.md
What list_watchtower_findings does on Sanka MCP Server
AI agents call list_watchtower_findings to retrieve information from Sanka MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_watchtower_findings is rated Low
This tool retrieves waste-related findings (renewal alerts, pricing analysis, vendor duplicates) from the WatchTower feature. It performs read-only operations with optional filtering. There are no side effects, data modifications, or external command executions.
From the tool's definition Tool name contains 'list' and description states it 'List[s] WatchTower waste findings' with 'optional status and finding_type filters'. The tool retrieves and queries findings data without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
The rule that runs list_watchtower_findings 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 list_watchtower_findings, this is the rule to start with:
list_watchtower_findings is read-only, so it stays allowed. 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 list_watchtower_findings call is checked against it from then on.
Questions about list_watchtower_findings
List WatchTower waste findings (upcoming renewals, vendor price creep, possibly duplicate vendors) in the authenticated workspace, with optional status and finding_type filters. Findings with buy_request_id already link to a Sanka Buy request. It is categorised as a Read tool in the Sanka MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for list_watchtower_findings: 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.
list_watchtower_findings 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 list_watchtower_findings 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 list_watchtower_findings. 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.
list_watchtower_findings 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