manage_aws_glue_crawler_management
AI agents call manage_aws_glue_crawler_management as a supporting operation in Amazon ECS MCP Server workflows.
Without a description, the exact action cannot be determined. 'Manage' could span Read, Write, Execute, or Destructive operations. AWS Glue crawlers can create/update/delete data catalog entries. Given the ambiguity, defaulting to 'Other' with low confidence, though Write or Execute would be plausible if more context were available.
From the tool's definition Tool description is empty and uninformative; tool name 'manage_aws_glue_crawler_management' suggests managing AWS Glue crawlers but exact behavior is unknown.
Documented attack patterns abuse exactly the kind of access manage_aws_glue_crawler_management gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon ECS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for manage_aws_glue_crawler_management:
{
"version": "1",
"default": "deny",
"tools": {
"manage_aws_glue_crawler_management": {
"limits": [
{
"counter": "manage_aws_glue_crawler_management_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
} manage_aws_glue_crawler_management gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
manage_aws_glue_crawler_management. It is categorised as a Other tool in the Amazon ECS MCP Server MCP Server, which means it performs auxiliary operations.
Register the Amazon ECS MCP Server MCP server in PolicyLayer and add a rule for manage_aws_glue_crawler_management: 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 ECS MCP Server. Nothing to install.
manage_aws_glue_crawler_management 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_crawler_management 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_crawler_management. 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_crawler_management is provided by the Amazon ECS MCP Server MCP server (awslabs.ecs-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Amazon ECS 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 ECS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.