Create a new AgentCore Policy Engine. COST WARNING: Creating a policy engine provisions AWS infrastructure and incurs AWS charges. The engine starts in CREATING status and transitions to ACTIVE when ready. Use policy_engine_get to poll the status. Returns the created policy engine details inclu...
Part of the AWS Bedrock AgentCore MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use policy_engine_create to create or modify resources in AWS Bedrock AgentCore MCP Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call policy_engine_create repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach AWS Bedrock AgentCore MCP Server.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
policy_engine_create:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full AWS Bedrock AgentCore MCP Server policy for all 122 tools.
Agents calling write-class tools like policy_engine_create have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Create a new AgentCore Policy Engine. COST WARNING: Creating a policy engine provisions AWS infrastructure and incurs AWS charges. The engine starts in CREATING status and transitions to ACTIVE when ready. Use policy_engine_get to poll the status. Returns the created policy engine details including its ID and ARN.. It is categorised as a Write tool in the AWS Bedrock AgentCore MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for policy_engine_create. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AWS Bedrock AgentCore MCP Server MCP server.
policy_engine_create 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 policy_engine_create rule in your Intercept 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 Intercept policy for policy_engine_create. 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.
policy_engine_create is provided by the AWS Bedrock AgentCore MCP Server MCP server (awslabs.amazon-bedrock-agentcore-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.