create_agent_runtime_endpoint
AI agents invoke create_agent_runtime_endpoint to trigger actions in AWS IoT SiteWise 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 name suggests creating a runtime endpoint for an agent, which implies provisioning or activating an execution environment. This leans toward Execute (deploying/activating a runtime resource) or Write (creating a resource). Given the 'runtime endpoint' framing implies an active, running component rather than just a data record, Execute is the most likely category.
From the tool's definition Tool name 'create_agent_runtime_endpoint' — description is empty and uninformative.
Attacks that exploit this kind of access
create_agent_runtime_endpoint. It is categorised as a Execute tool in the AWS IoT SiteWise MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AWS IoT SiteWise 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 AWS IoT SiteWise 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 AWS IoT SiteWise MCP Server MCP server (awslabs.aws-iot-sitewise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.