AI agents use create_agent_runtime to create or update resources in Amazon Data Processing MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Amazon Data Processing MCP Server environment.
The name 'create_agent_runtime' strongly implies creating a new agent runtime resource (likely an AWS Bedrock or similar agent execution environment), which is a Write operation. However, the empty description lowers confidence significantly. Given the server context (AWS data processing MCP), this likely provisions a new runtime environment.
From the tool's definition Tool name: create_agent_runtime — 'create' prefix suggests resource creation; description is empty/uninformative.
Documented attack patterns abuse exactly the kind of access create_agent_runtime gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon Data Processing MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_agent_runtime:
{
"version": "1",
"default": "deny",
"tools": {
"create_agent_runtime": {
"limits": [
{
"counter": "create_agent_runtime_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_agent_runtime 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.
create_agent_runtime. It is categorised as a Write tool in the Amazon Data Processing MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Amazon Data Processing MCP Server MCP server in PolicyLayer and add a rule for create_agent_runtime: 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 Data Processing MCP Server. Nothing to install.
create_agent_runtime 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 create_agent_runtime 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 create_agent_runtime. 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.
create_agent_runtime is provided by the Amazon Data Processing MCP Server MCP server (awslabs.aws-dataprocessing-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Amazon Data Processing 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 Data Processing MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.