start_security_scan
AI agents invoke start_security_scan to trigger actions in AWS Labs Amazon Q Business anonymous mode MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Security scans are Execute-class tools because they trigger external operations (security analysis processes) whose side effects depend on what is scanned and how the scan is configured. While scans themselves are non-destructive reads of system state, initiating them is an active operation that could consume resources, trigger alerts, or expose sensitive information in scan results.
From the tool's definition Tool name 'start_security_scan' indicates initiation of a scanning operation. The tool description is empty, but the name suggests triggering an external security scanning process whose effects depend on runtime arguments and target configuration.
Documented attack patterns abuse exactly the kind of access start_security_scan gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS Labs Amazon Q Business anonymous mode MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for start_security_scan:
{
"version": "1",
"default": "deny",
"tools": {
"start_security_scan": {
"limits": [
{
"counter": "start_security_scan_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} start_security_scan stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
All 805 AWS Labs Amazon Q Business anonymous mode MCP Server tools →
start_security_scan. It is categorised as a Execute tool in the AWS Labs Amazon Q Business anonymous mode MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AWS Labs Amazon Q Business anonymous mode MCP Server MCP server in PolicyLayer and add a rule for start_security_scan: 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 AWS Labs Amazon Q Business anonymous mode MCP Server. Nothing to install.
start_security_scan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the start_security_scan 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 start_security_scan. 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.
start_security_scan is provided by the AWS Labs Amazon Q Business anonymous mode MCP Server MCP server (awslabs.amazon-qbusiness-anonymous-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS Labs Amazon Q Business anonymous mode MCP Server, 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.
805 AWS Labs Amazon Q Business anonymous mode MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.