manage_aws_glue_tables
AI agents use manage_aws_glue_tables to create or update resources in Amazon MQ MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Amazon MQ MCP Server environment.
Without an explicit description, this tool's scope is ambiguous. However, 'manage' in AWS contexts usually means reversible modification of resources (creating tables, updating schemas, modifying properties) rather than deletion. This places it in the Write category rather than Destructive.
From the tool's definition Tool name 'manage_aws_glue_tables' indicates data modification operations on AWS Glue tables. While the description is empty, the verb 'manage' typically encompasses create, update, and modify operations on table metadata and schemas.
Attacks that exploit this kind of access
manage_aws_glue_tables. It is categorised as a Write tool in the Amazon MQ MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Amazon MQ MCP Server MCP server in PolicyLayer and add a rule for manage_aws_glue_tables: 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 Amazon MQ MCP Server. Nothing to install.
manage_aws_glue_tables 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 manage_aws_glue_tables 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_tables. 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_tables is provided by the Amazon MQ MCP Server MCP server (awslabs.amazon-mq-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.