start_security_scan · Awslabs Valkey MCP: Risk & Policy

WHAT IT DOES

What start_security_scan does on Awslabs Valkey

AI agents invoke start_security_scan to trigger actions in Awslabs Valkey. 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.

WHY IT NEEDS A POLICY

Why start_security_scan needs a policy

The tool initiates a security scan operation, which is an active execution that triggers external processes or monitoring jobs on AWS infrastructure. Without a description, we cannot confirm if it merely queues a scan (Execute) or has side effects. The 'start' verb and security-scanning context suggest it runs or schedules operations whose effects depend on how the scan is configured, fitting Execute category.

From the tool's definition Tool named 'start_security_scan' with empty description; verb 'start' indicates triggering an operation; context of AWS ElastiCache/MemoryDB Valkey suggests initiation of a security scanning process on cloud resources

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_security_scan Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_security_scan": {
      "limits": [
        {
          "counter": "start_security_scan_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Awslabs Valkey, so you can run agents against it safely.

FAQ

Questions about start_security_scan

What does the start_security_scan tool do? +

start_security_scan. It is categorised as a Execute tool in the Awslabs Valkey MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on start_security_scan? +

Register the Awslabs Valkey 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 Awslabs Valkey. Nothing to install.

What risk level is start_security_scan? +

start_security_scan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_security_scan? +

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.

How do I block start_security_scan completely? +

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.

What MCP server provides start_security_scan? +

start_security_scan is provided by the Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.