create_terminology
AI agents use create_terminology 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 new data (terminology entries) but does not irreversibly delete, execute arbitrary code, or move funds. The empty description reduces confidence but the 'create_' prefix indicates Write operations. Severity is medium because misuse could add incorrect broker configuration or management terminology, causing operational confusion but not permanent loss.
From the tool's definition Tool name 'create_terminology' combined with server context (Amazon MQ provisioning/management) suggests creating or defining new terminology entries, likely configuration or reference data.
Attacks that exploit this kind of access
create_terminology. 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_terminology: 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_terminology 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_terminology 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_terminology. 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_terminology 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.