AI agents use scf_add_custom_risk_control to create or update resources in Scf — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Scf environment.
This tool creates or modifies data by establishing a link between existing entities. The action is reversible (the link could theoretically be removed), and there is no deletion, destruction, or financial impact.
From the tool's definition The tool description explicitly states 'write — editor+ role' and the operation is 'Link a scoped control to a custom risk', which creates or modifies an association between two entities (a control and a custom risk).
Attacks that exploit this kind of access
Link a scoped control to a custom risk (write — editor+ role). The control must already be scoped (in-scope) for this organization. It is categorised as a Write tool in the Scf MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Scf MCP server in PolicyLayer and add a rule for scf_add_custom_risk_control: 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_add_custom_risk_control 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 scf_add_custom_risk_control 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_add_custom_risk_control. 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_add_custom_risk_control 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 →