get_capabilities

THE RISK

Low Risk

Why get_capabilities needs a policy

This tool retrieves capability information about the O3DE system. It performs no modifications, executions, or destructive actions. The name pattern and context within an automation server suggest it queries available features or system state, making it a Read operation with low risk.

From the tool's definition Tool name 'get_capabilities' indicates information retrieval with no parameters or side effects mentioned.

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

POLICY

How to control get_capabilities

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_capabilities": {}
  }
}

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

Create a free account and register O3de — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More O3de tools

Destructive delete_entity Delete an entity from the current O3DE level. Execute build_project Build an O3DE project using CMake. Execute run_editor_python run_editor_python Execute load_level Open a level in the O3DE Editor. Execute enter_game_mode Enter game mode (play-in-editor) in the O3DE Editor. Execute exit_game_mode Exit game mode and return to edit mode. Write add_component Add a component to an entity. Write create_entity Create a new entity in the current O3DE level.

All 30 O3de tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_capabilities

What does the get_capabilities tool do? +

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

How do I enforce a policy on get_capabilities? +

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

What risk level is get_capabilities? +

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

Can I rate-limit get_capabilities? +

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

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

get_capabilities is provided by the O3de MCP server (nickschuetz/o3de-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every O3de tool call.

Start from O3de, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →