manage_aws_glue_triggers
AI agents invoke manage_aws_glue_triggers 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 managing AWS Glue triggers, which control the execution of ETL jobs and workflows. 'Manage' implies creating, updating, enabling, disabling, or deleting triggers — spanning Write, Execute, and potentially Destructive actions. Since it can trigger execution of Glue jobs and may allow deletion of triggers, Execute is the most appropriate base category given the operational impact.
From the tool's definition Tool name 'manage_aws_glue_triggers' — no description provided.
Attacks that exploit this kind of access
manage_aws_glue_triggers. 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 manage_aws_glue_triggers: 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.
manage_aws_glue_triggers 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 manage_aws_glue_triggers 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 manage_aws_glue_triggers. 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.
manage_aws_glue_triggers 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.