Clear the Stale Progress flag (col AF) for a metro without changing its tier. Use this when you've reviewed the CRITICAL_NEGATIVE event and decided the existing Published Tier (AE) is still accurate — no tier change needed. If you ARE changing the tier, use set_published_tier instead (it clears A...
Part of the Cap Rate Signals server.
Free to start. No card required.
AI agents may call clear_stale_progress_flag to permanently remove or destroy resources in Cap Rate Signals. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call clear_stale_progress_flag in a loop, permanently destroying resources in Cap Rate Signals. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"clear_stale_progress_flag"
]
}See the full Cap Rate Signals policy for all 14 tools.
These attack patterns abuse exactly the kind of access clear_stale_progress_flag gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Clear the Stale Progress flag (col AF) for a metro without changing its tier. Use this when you've reviewed the CRITICAL_NEGATIVE event and decided the existing Published Tier (AE) is still accurate — no tier change needed. If you ARE changing the tier, use set_published_tier instead (it clears AF automatically). Trigger phrases: 'clear the stale flag for X', 'dismiss the alert for X', 'flag resolved for X', 'no tier change needed for X — clear it', 'Indianapolis stale flag — reviewed and OK'. It is categorised as a Destructive tool in the Cap Rate Signals MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Cap Rate Signals MCP server in PolicyLayer and add a rule for clear_stale_progress_flag: 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 Cap Rate Signals. Nothing to install.
clear_stale_progress_flag is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clear_stale_progress_flag 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 clear_stale_progress_flag. 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.
clear_stale_progress_flag is provided by the Cap Rate Signals MCP server (capratesignals/cap-rate-signals). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 Cap Rate Signals tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.