Clear both the backend API cache and the solver oracle cache to force fresh fetches on next requests. Reports the number of entries cleared per cache.
Part of the SODAX Builders MCP server.
Free to start. No card required.
AI agents may call sodax_refresh_cache to permanently remove or destroy resources in SODAX Builders MCP. 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 sodax_refresh_cache in a loop, permanently destroying resources in SODAX Builders MCP. 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": [
"sodax_refresh_cache"
]
}See the full SODAX Builders MCP policy for all 38 tools.
These attack patterns abuse exactly the kind of access sodax_refresh_cache 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 both the backend API cache and the solver oracle cache to force fresh fetches on next requests. Reports the number of entries cleared per cache.. It is categorised as a Destructive tool in the SODAX Builders MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the SODAX Builders MCP server in PolicyLayer and add a rule for sodax_refresh_cache: 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 SODAX Builders MCP. Nothing to install.
sodax_refresh_cache 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 sodax_refresh_cache 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 sodax_refresh_cache. 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.
sodax_refresh_cache is provided by the SODAX Builders MCP server (https://builders.sodax.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 38 SODAX Builders MCP 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.