manage_aws_glue_sessions
AI agents invoke manage_aws_glue_sessions to trigger actions in AWS Step Functions Tool 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.
The description is empty, so confidence is lowered. However, 'manage' in the context of AWS Glue sessions typically implies lifecycle operations (create, start, stop, delete) on interactive sessions that can execute Spark/Python code. This spans Write, Execute, and potentially Destructive categories. Given that Glue sessions are execution environments, Execute is the most appropriate category.
From the tool's definition Tool name 'manage_aws_glue_sessions' suggests creating, modifying, or terminating AWS Glue interactive sessions, which are execution environments for running data processing code.
Documented attack patterns abuse exactly the kind of access manage_aws_glue_sessions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS Step Functions Tool MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for manage_aws_glue_sessions:
{
"version": "1",
"default": "deny",
"tools": {
"manage_aws_glue_sessions": {
"limits": [
{
"counter": "manage_aws_glue_sessions_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} manage_aws_glue_sessions 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.
Free to start. No card required.
manage_aws_glue_sessions. It is categorised as a Execute tool in the AWS Step Functions Tool MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AWS Step Functions Tool MCP Server MCP server in PolicyLayer and add a rule for manage_aws_glue_sessions: 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 Step Functions Tool MCP Server. Nothing to install.
manage_aws_glue_sessions is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the manage_aws_glue_sessions 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_sessions. 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_sessions is provided by the AWS Step Functions Tool MCP Server MCP server (awslabs.stepfunctions-tool-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS Step Functions Tool 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 AWS Step Functions Tool MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.