create_resolver
AI agents use create_resolver to create or update resources in Amazon MQ MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Amazon MQ MCP Server environment.
The tool creates a resolver resource within the Amazon MQ ecosystem, which is a reversible write operation. Without explicit details on whether this resolver controls message routing, access control, or network behavior, the baseline classification is Write. Severity is medium because misuse could misdirect message traffic or cause operational disruption, but effects are not destructive or financial.
From the tool's definition Tool name 'create_resolver' and server context (Amazon MQ management). The 'create_' prefix indicates a data creation/modification operation. Empty description limits certainty.
Attacks that exploit this kind of access
create_resolver. It is categorised as a Write tool in the Amazon MQ MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Amazon MQ MCP Server MCP server in PolicyLayer and add a rule for create_resolver: 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.
create_resolver is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_resolver 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 create_resolver. 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.
create_resolver 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.