Low Risk

policy_engine_list

policy_engine_list

How to control policy_engine_list ↓

What policy_engine_list does on Amazon Translate MCP Server

AI agents call policy_engine_list to retrieve information from Amazon Translate MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why policy_engine_list needs a policy

The naming convention 'list' strongly indicates data retrieval with no side effects. However, confidence is reduced due to lack of description. Without evidence of mutation, deletion, or execution, the most reasonable classification is Read. The tool appears to be querying policy engine information rather than modifying it.

From the tool's definition Tool name 'policy_engine_list' suggests a list/query operation typical of Read operations. No description provided to confirm exact functionality.

Documented attack patterns abuse exactly the kind of access policy_engine_list gives an agent:

How to control policy_engine_list

PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon Translate MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for policy_engine_list:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "policy_engine_list": {}
  }
}

policy_engine_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Amazon Translate MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about policy_engine_list

What does the policy_engine_list tool do? +

policy_engine_list. It is categorised as a Read tool in the Amazon Translate MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on policy_engine_list? +

Register the Amazon Translate MCP Server MCP server in PolicyLayer and add a rule for policy_engine_list: 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 Translate MCP Server. Nothing to install.

What risk level is policy_engine_list? +

policy_engine_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit policy_engine_list? +

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

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

policy_engine_list is provided by the Amazon Translate MCP Server MCP server (awslabs.amazon-translate-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Amazon Translate MCP Server tool call.

Start from Amazon Translate MCP Server, 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.

805 Amazon Translate MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.