AI agents invoke CreateAHORunGroup to trigger actions in AWS API MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The description is empty, so classification is based solely on the tool name. 'Create' typically implies a Write operation, but 'RunGroup' in AWS HealthOmics context is a resource that governs execution of workflow runs. Given the ambiguity and the 'Run' component suggesting execution semantics, Execute is selected as the more severe applicable category. Confidence is low due to the empty description.
From the tool's definition Tool name 'CreateAHORunGroup' suggests creating a run group (likely AWS HealthOmics run group), which involves executing/creating a resource on AWS.
Documented attack patterns abuse exactly the kind of access CreateAHORunGroup gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS API MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for CreateAHORunGroup:
{
"version": "1",
"default": "deny",
"tools": {
"CreateAHORunGroup": {
"limits": [
{
"counter": "createahorungroup_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}CreateAHORunGroup stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
CreateAHORunGroup. It is categorised as a Execute tool in the AWS API MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AWS API MCP Server MCP server in PolicyLayer and add a rule for CreateAHORunGroup: 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 AWS API MCP Server. Nothing to install.
CreateAHORunGroup is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the CreateAHORunGroup 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 CreateAHORunGroup. 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.
CreateAHORunGroup is provided by the AWS API MCP Server MCP server (awslabs.aws-api-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS API 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 AWS API MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.