deploy_serverless_app_help
AI agents invoke deploy_serverless_app_help to trigger actions in AWS Bedrock AgentCore 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.
Deploying serverless applications triggers external operations and infrastructure changes whose effects depend on arguments (which application, configuration, version to deploy). This constitutes Execute category rather than Write because deployment actions are typically orchestrated operations affecting live infrastructure.
From the tool's definition Tool name 'deploy_serverless_app_help' indicates deployment of serverless applications. The name suggests execution of infrastructure-as-code or deployment automation.
Attacks that exploit this kind of access
deploy_serverless_app_help. It is categorised as a Execute tool in the AWS Bedrock AgentCore MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AWS Bedrock AgentCore MCP Server MCP server in PolicyLayer and add a rule for deploy_serverless_app_help: 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 Bedrock AgentCore MCP Server. Nothing to install.
deploy_serverless_app_help 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 deploy_serverless_app_help 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 deploy_serverless_app_help. 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.
deploy_serverless_app_help is provided by the AWS Bedrock AgentCore MCP Server MCP server (awslabs.amazon-bedrock-agentcore-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.