manage_aws_glue_crawlers
AI agents call manage_aws_glue_crawlers as a supporting operation in Amazon ElastiCache Memcached MCP Server workflows.
The description is empty, so the tool's behavior cannot be determined from it. The name 'manage_aws_glue_crawlers' suggests managing AWS Glue crawlers (which can read, write, execute, or configure data catalog crawlers), but without a description, the exact action scope is unknown. Given 'manage' is ambiguous and could span Read/Write/Execute, I assign 'Other' with low confidence and medium severity as a precaution.
From the tool's definition Tool name: manage_aws_glue_crawlers; description is empty and uninformative
Attacks that exploit this kind of access
manage_aws_glue_crawlers. It is categorised as a Other tool in the Amazon ElastiCache Memcached MCP Server MCP Server, which means it performs auxiliary operations.
Register the Amazon ElastiCache Memcached MCP Server MCP server in PolicyLayer and add a rule for manage_aws_glue_crawlers: 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 ElastiCache Memcached MCP Server. Nothing to install.
manage_aws_glue_crawlers 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_crawlers 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_crawlers. 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_crawlers is provided by the Amazon ElastiCache Memcached MCP Server MCP server (awslabs.memcached-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.