High Risk →

manage_aws_glue_statements

manage_aws_glue_statements

How to control manage_aws_glue_statements ↓

What manage_aws_glue_statements does on Amazon Bedrock Knowledge Base Retrieval MCP Server

AI agents invoke manage_aws_glue_statements to trigger actions in Amazon Bedrock Knowledge Base Retrieval 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.

High Risk

Why manage_aws_glue_statements needs a policy

AWS Glue statements typically refer to code statements executed within Glue interactive sessions or ETL jobs. 'Manage' could span multiple operations including creating, running, and canceling statements. Since Glue statements involve executing code/queries, the Execute category is most appropriate. Severity is high due to potential data processing impact and AWS resource consumption.

From the tool's definition Tool name 'manage_aws_glue_statements' suggests managing AWS Glue statements, which typically involves executing ETL jobs, running queries, or managing data processing workflows in AWS Glue interactive sessions.

Documented attack patterns abuse exactly the kind of access manage_aws_glue_statements gives an agent:

How to control manage_aws_glue_statements

PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon Bedrock Knowledge Base Retrieval MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for manage_aws_glue_statements:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "manage_aws_glue_statements": {
      "limits": [
        {
          "counter": "manage_aws_glue_statements_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

manage_aws_glue_statements stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Amazon Bedrock Knowledge Base Retrieval MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about manage_aws_glue_statements

What does the manage_aws_glue_statements tool do? +

manage_aws_glue_statements. It is categorised as a Execute tool in the Amazon Bedrock Knowledge Base Retrieval MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on manage_aws_glue_statements? +

Register the Amazon Bedrock Knowledge Base Retrieval MCP Server MCP server in PolicyLayer and add a rule for manage_aws_glue_statements: 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 Bedrock Knowledge Base Retrieval MCP Server. Nothing to install.

What risk level is manage_aws_glue_statements? +

manage_aws_glue_statements is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit manage_aws_glue_statements? +

Yes. Add a rate_limit block to the manage_aws_glue_statements 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.

How do I block manage_aws_glue_statements completely? +

Set action: deny in the PolicyLayer policy for manage_aws_glue_statements. 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.

What MCP server provides manage_aws_glue_statements? +

manage_aws_glue_statements is provided by the Amazon Bedrock Knowledge Base Retrieval MCP Server MCP server (awslabs.bedrock-kb-retrieval-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Amazon Bedrock Knowledge Base Retrieval MCP Server tool call.

Start from Amazon Bedrock Knowledge Base Retrieval MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

805 Amazon Bedrock Knowledge Base Retrieval MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.