Get the currently running task, if any. Returns null if no task is currently in progress.
AI agents call bytebot_get_in_progress_task to retrieve information from ByteBot MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries the state of a running task and returns data without modifying, deleting, executing, or triggering any operations. It is a simple status check operation analogous to a GET request in REST APIs, making it a Read category tool with low severity since it merely observes system state.
From the tool's definition Tool name is 'bytebot_get_in_progress_task' and description states it 'Get[s] the currently running task, if any. Returns null if no task is currently in progress.' This is a pure retrieval operation with no side effects.
Attacks that exploit this kind of access
Get the currently running task, if any. Returns null if no task is currently in progress. It is categorised as a Read tool in the ByteBot MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ByteBot MCP Server MCP server in PolicyLayer and add a rule for bytebot_get_in_progress_task: 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 ByteBot MCP Server. Nothing to install.
bytebot_get_in_progress_task is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the bytebot_get_in_progress_task 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 bytebot_get_in_progress_task. 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.
bytebot_get_in_progress_task is provided by the ByteBot MCP Server MCP server (sensuslab/spark-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →