Delete a custom risk definition, its assessment record, and every control mapping (destructive write — editor+ role). Irreversible.
AI agents call scf_delete_custom_risk to permanently remove resources in Scf — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes custom risk definitions, assessment records, and all associated control mappings. The blast radius is high: deletion of risk records could break compliance tracking, orphan controls, and prevent audit trail reconstruction.
From the tool's definition Tool description explicitly states: 'Delete a custom risk definition, its assessment record, and every control mapping (destructive write — editor+ role).
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Delete a custom risk definition, its assessment record, and every control mapping (destructive write — editor+ role). Irreversible. It is categorised as a Destructive tool in the Scf MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Scf MCP server in PolicyLayer and add a rule for scf_delete_custom_risk: 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 Scf. Nothing to install.
scf_delete_custom_risk 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 scf_delete_custom_risk 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 scf_delete_custom_risk. 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.
scf_delete_custom_risk is provided by the Scf MCP server (mcp-server-scf). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →