create_ecs_infrastructure

WHAT IT DOES

What create_ecs_infrastructure does on Amazon ElastiCache Memcached MCP Server

AI agents use create_ecs_infrastructure 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_ecs_infrastructure needs a policy

The tool name implies creating cloud infrastructure (ECS resources such as clusters, services, task definitions), which is a Write operation with potentially high blast radius. However, the description is empty, lowering confidence. Creating infrastructure is reversible (resources can be deleted), so Write is appropriate rather than Destructive.

From the tool's definition Tool name 'create_ecs_infrastructure' suggests creation of ECS (Elastic Container Service) infrastructure resources.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_ecs_infrastructure Rate-limited

create_ecs_infrastructure 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_ecs_infrastructure": {
      "limits": [
        {
          "counter": "create_ecs_infrastructure_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_ecs_infrastructure

What does the create_ecs_infrastructure tool do? +

create_ecs_infrastructure. 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_ecs_infrastructure? +

Register the Amazon ElastiCache Memcached MCP Server MCP server in PolicyLayer and add a rule for create_ecs_infrastructure: 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_ecs_infrastructure? +

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

Can I rate-limit create_ecs_infrastructure? +

Yes. Add a rate_limit block to the create_ecs_infrastructure 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_ecs_infrastructure completely? +

Set action: deny in the PolicyLayer policy for create_ecs_infrastructure. 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_ecs_infrastructure? +

create_ecs_infrastructure 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.