list_agent_runtime_endpoints
AI agents call list_agent_runtime_endpoints to retrieve information from Amazon MQ MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name follows the 'list_' pattern, which is a standard convention for read operations that retrieve or query existing data. The empty description is a limitation, but the naming convention is sufficiently clear that this retrieves endpoint information without side effects. No indicators of modification, deletion, execution, or financial operations are present.
From the tool's definition Tool name 'list_agent_runtime_endpoints' indicates a listing/querying operation that retrieves information about agent runtime endpoints without modification.
Attacks that exploit this kind of access
list_agent_runtime_endpoints. It is categorised as a Read tool in the Amazon MQ MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Amazon MQ MCP Server MCP server in PolicyLayer and add a rule for list_agent_runtime_endpoints: 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.
list_agent_runtime_endpoints is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_agent_runtime_endpoints 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 list_agent_runtime_endpoints. 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.
list_agent_runtime_endpoints 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.