schedule_stop_application · Awslabs Valkey MCP

WHAT IT DOES

What schedule_stop_application does on Awslabs Valkey

AI agents invoke schedule_stop_application 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 schedule_stop_application needs a policy

The tool name suggests it schedules or triggers a stop operation on an application, which is an external operational action (Execute category). Stopping an application can have significant impact (high severity) if misused. The empty description reduces confidence, but the name strongly implies an Execute-level action rather than a simple read or write.

From the tool's definition Tool name 'schedule_stop_application' implies triggering an operational action (stopping an application on a schedule). Description is empty, which lowers confidence.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

schedule_stop_application Rate-limited

schedule_stop_application 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": {
    "schedule_stop_application": {
      "limits": [
        {
          "counter": "schedule_stop_application_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 schedule_stop_application

What does the schedule_stop_application tool do? +

schedule_stop_application. 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 schedule_stop_application? +

Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for schedule_stop_application: 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 schedule_stop_application? +

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

Can I rate-limit schedule_stop_application? +

Yes. Add a rate_limit block to the schedule_stop_application 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 schedule_stop_application completely? +

Set action: deny in the PolicyLayer policy for schedule_stop_application. 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 schedule_stop_application? +

schedule_stop_application 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.