create_terminology | PolicyLayer

WHAT IT DOES

What create_terminology does on Amazon ElastiCache Memcached MCP Server

AI agents use create_terminology to create or update resources in Amazon ElastiCache Memcached MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Amazon ElastiCache Memcached MCP Server environment.

WHY IT NEEDS A POLICY

Why create_terminology needs a policy

The tool name 'create_terminology' indicates creation of new data (terminology records), fitting the Write category. Without a description, confidence is moderate. Given the ElastiCache Memcached server context and similar sibling tools that modify AWS state, this is classified as Write rather than Read.

From the tool's definition Tool name 'create_terminology' suggests data creation. Description is empty, limiting direct evidence. Context from sibling tools (add_attachments, add_communication, add_inline_policy, add_user_to_group) shows this server performs write operations on AWS…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_terminology Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_terminology": {
      "limits": [
        {
          "counter": "create_terminology_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Amazon ElastiCache Memcached MCP Server, so you can run agents against it safely.

FAQ

Questions about create_terminology

What does the create_terminology tool do? +

create_terminology. It is categorised as a Write tool in the Amazon ElastiCache Memcached MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_terminology? +

Register the Amazon ElastiCache Memcached 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 ElastiCache Memcached MCP Server. Nothing to install.

What risk level is create_terminology? +

create_terminology is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_terminology? +

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.

How do I block create_terminology completely? +

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.

What MCP server provides create_terminology? +

create_terminology is provided by the Amazon ElastiCache Memcached MCP Server MCP server (awslabs.memcached-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.