Medium Risk

identity_put_resource_policy

Create or replace the resource-based policy on an AgentCore resource. ACCESS CONTROL WARNING: This modifies who can invoke or manage the target resource. Overly permissive policies (e.g. broad Principal wildcards or cross-account access) can expose the resource to unintended callers. Review poli...

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 identity_put_resource_policy 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 identity_put_resource_policy 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.

aws-bedrock-agentcore-mcp-server.yaml
tools:
  identity_put_resource_policy:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full AWS Bedrock AgentCore MCP Server policy for all 122 tools.

Tool Name identity_put_resource_policy
Category Write
Risk Level Medium

View all 122 tools →

Agents calling write-class tools like identity_put_resource_policy have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the identity_put_resource_policy tool do? +

Create or replace the resource-based policy on an AgentCore resource. ACCESS CONTROL WARNING: This modifies who can invoke or manage the target resource. Overly permissive policies (e.g. broad Principal wildcards or cross-account access) can expose the resource to unintended callers. Review policy documents carefully before applying, and prefer least-privilege statements scoped to specific principals and actions. This is an idempotent replace — it overwrites any existing policy on the resource.. 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.

How do I enforce a policy on identity_put_resource_policy? +

Add a rule in your Intercept YAML policy under the tools section for identity_put_resource_policy. 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.

What risk level is identity_put_resource_policy? +

identity_put_resource_policy is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit identity_put_resource_policy? +

Yes. Add a rate_limit block to the identity_put_resource_policy 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.

How do I block identity_put_resource_policy completely? +

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

identity_put_resource_policy 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.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.