stop_application
AI agents invoke stop_application to trigger actions in Amazon MQ 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.
Stopping an application is an operational action that triggers external effects (service interruption, potential data loss in-flight, service unavailability) but is reversible via restart. This falls under Execute rather than Destructive since the action is not permanent.
From the tool's definition Tool name 'stop_application' on Amazon MQ MCP Server indicates it stops/halts a running application or service. The description is empty, limiting direct textual evidence.
Attacks that exploit this kind of access
stop_application. It is categorised as a Execute tool in the Amazon MQ MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Amazon MQ MCP Server MCP server in PolicyLayer and add a rule for 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 Amazon MQ MCP Server. Nothing to install.
stop_application 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 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.
Set action: deny in the PolicyLayer policy for 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.
stop_application is provided by the Amazon MQ MCP Server MCP server (awslabs.amazon-mq-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.