Update the status of a security finding
AI agents use update_security_finding_status to create or update resources in RAD Security — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RAD Security environment.
This tool modifies data (security finding status) in a reversible manner. It does not delete or destroy data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read). Status updates can typically be reverted or changed again, making it a Write operation.
From the tool's definition Tool name 'update_security_finding_status' and description 'Update the status of a security finding' indicate a modification operation that changes the state of an existing security record.
Documented attack patterns abuse exactly the kind of access update_security_finding_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and RAD Security, and nothing reaches the server without passing your rules. This is the rule we recommend for update_security_finding_status:
{
"version": "1",
"default": "deny",
"tools": {
"update_security_finding_status": {
"limits": [
{
"counter": "update_security_finding_status_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_security_finding_status stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update the status of a security finding. It is categorised as a Write tool in the RAD Security MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RAD Security MCP server in PolicyLayer and add a rule for update_security_finding_status: 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 RAD Security. Nothing to install.
update_security_finding_status 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 update_security_finding_status 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 update_security_finding_status. 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.
update_security_finding_status is provided by the RAD Security MCP server (rad-security/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from RAD Security, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
55 RAD Security tools catalogued and risk-classified — across an index of 43,000+ MCP servers.