This record as markdown: /tools/aws/create-terminology.md
What create_terminology does on AWS
AI agents use create_terminology to create or update resources in AWS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AWS environment.
Why create_terminology is rated Medium
The tool name indicates a Create operation, which is Write-category by default. Without a description, confidence is reduced. Medium severity assumes this creates terminology entries (likely reversible via update/delete) with moderate blast radius if an AI agent misuses it to create malicious or incorrect terminology entries.
From the tool's definition Tool name 'create_terminology' suggests data creation. No description provided to confirm scope or reversibility.
Attacks that exploit this kind of access
The rule that runs create_terminology safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AWS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_terminology, this is the rule to start with:
create_terminology stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AWS, apply this rule, and every create_terminology call is checked against it from then on.
Questions about create_terminology
create_terminology is a write tool on the AWS MCP server. It is categorised as a Write tool in the AWS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AWS 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 AWS. 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 AWS MCP server (@awslabs/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AWS, and thousands of servers like it.
This server
Across the catalogue