AI agents use scf_update_vendor 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 modifies existing vendor data in the SCF Controls Platform compliance system. It is a write operation that updates records reversibly. The severity is medium because vendor records in a compliance platform could affect trust decisions, access controls, or regulatory assessments if maliciously altered, but the impact is limited to a single vendor entity and is not destructive or financial in nature.
From the tool's definition Tool description explicitly states 'Update an existing vendor record (write — editor+ role). Only provided fields are applied.'
Attacks that exploit this kind of access
Update an existing vendor record (write — editor+ role). Only provided fields are applied. 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_update_vendor: 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_update_vendor 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_update_vendor 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_update_vendor. 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_update_vendor 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 →