create_agent_runtime_endpoint
AI agents invoke create_agent_runtime_endpoint to trigger actions in Amazon Bedrock Knowledge Base Retrieval 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 tool name suggests creating a runtime endpoint for an agent, which implies provisioning or activating infrastructure/services. This is at minimum a Write operation, but 'runtime endpoint' creation typically triggers external operational resources or executes deployments, placing it in Execute category. However, the description is empty so confidence is lowered.
From the tool's definition Tool name: 'create_agent_runtime_endpoint' — no description provided
Documented attack patterns abuse exactly the kind of access create_agent_runtime_endpoint gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon Bedrock Knowledge Base Retrieval MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_agent_runtime_endpoint:
{
"version": "1",
"default": "deny",
"tools": {
"create_agent_runtime_endpoint": {
"limits": [
{
"counter": "create_agent_runtime_endpoint_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} create_agent_runtime_endpoint 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.
All 805 Amazon Bedrock Knowledge Base Retrieval MCP Server tools →
create_agent_runtime_endpoint. It is categorised as a Execute tool in the Amazon Bedrock Knowledge Base Retrieval MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Amazon Bedrock Knowledge Base Retrieval MCP Server MCP server in PolicyLayer and add a rule for create_agent_runtime_endpoint: 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 Bedrock Knowledge Base Retrieval MCP Server. Nothing to install.
create_agent_runtime_endpoint 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 create_agent_runtime_endpoint 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_endpoint. 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_endpoint is provided by the Amazon Bedrock Knowledge Base Retrieval MCP Server MCP server (awslabs.bedrock-kb-retrieval-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Amazon Bedrock Knowledge Base Retrieval 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 Bedrock Knowledge Base Retrieval MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.