manage_aws_glue_usage_profiles
AI agents call manage_aws_glue_usage_profiles as a supporting operation in AWS IoT SiteWise MCP Server workflows.
The description is empty, so the category must be inferred from the name alone. 'Manage' is ambiguous and could span Read, Write, or Destructive operations. AWS Glue usage profiles relate to configuration/resource management. Without further detail, confidence is low. 'Manage' most commonly implies Write-level operations (create/update), but could include delete.
From the tool's definition Tool name is 'manage_aws_glue_usage_profiles' but description is empty/uninformative.
Attacks that exploit this kind of access
manage_aws_glue_usage_profiles. It is categorised as a Other tool in the AWS IoT SiteWise MCP Server MCP Server, which means it performs auxiliary operations.
Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for manage_aws_glue_usage_profiles: 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_usage_profiles is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the manage_aws_glue_usage_profiles 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_usage_profiles. 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_usage_profiles 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.