Create an OAuth2 credential provider in AgentCore Identity. COST WARNING: Creates a secret in AWS Secrets Manager (holding the client_secret) and incurs Secrets Manager storage charges. SECURITY NOTE: The clientSecret inside oauth2_provider_config_input flows through LLM context when this tool ...
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_create_oauth2_provider 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_create_oauth2_provider 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:
identity_create_oauth2_provider:
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 identity_create_oauth2_provider 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 an OAuth2 credential provider in AgentCore Identity. COST WARNING: Creates a secret in AWS Secrets Manager (holding the client_secret) and incurs Secrets Manager storage charges. SECURITY NOTE: The clientSecret inside oauth2_provider_config_input flows through LLM context when this tool is called by an AI assistant. For production secrets, strongly prefer the CLI: agentcore add credential --name <n> --type oauth \ --discovery-url <url> --client-id <id> \ --client-secret <secret> --scopes <scope1,scope2> The CLI accepts the secret without it entering LLM conversation history. Use this MCP tool for test providers, automation from controlled contexts, or when the client_secret is already known to the caller. The response includes a callbackUrl — the OAuth2 redirect URI you must register with the external provider.. 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 identity_create_oauth2_provider. 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.
identity_create_oauth2_provider 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 identity_create_oauth2_provider 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 identity_create_oauth2_provider. 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.
identity_create_oauth2_provider 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.