AI agents use import_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.
Without a description, confidence is reduced. However, 'import' most commonly means ingesting and storing data (Write category). On an AWS server managing translations and policies, importing terminology likely populates a database or configuration store. This is reversible (unlike Destructive) but modifies system state.
From the tool's definition Tool name 'import_terminology' suggests creating or adding terminology data. The empty description prevents definitive classification, but 'import' typically denotes a write/creation operation.
Documented attack patterns abuse exactly the kind of access import_terminology gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS, and nothing reaches the server without passing your rules. This is the rule we recommend for import_terminology:
{
"version": "1",
"default": "deny",
"tools": {
"import_terminology": {
"limits": [
{
"counter": "import_terminology_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}import_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.
Free to start. No card required.
import_terminology. 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 import_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.
import_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 import_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 import_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.
import_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.
Start from AWS, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
300 AWS tools catalogued and risk-classified — across an index of 43,000+ MCP servers.