Get the current status of a task. Returns status, timestamps, and basic info.
AI agents call get-task-status to retrieve information from Back-Agent MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries task status information and returns metadata (status, timestamps, basic info) without altering state, executing code, or triggering operations. It is a straightforward read operation with minimal security risk even if misused by an AI agent.
From the tool's definition Tool name 'get-task-status' and description 'Get the current status of a task. Returns status, timestamps, and basic info.' indicate pure retrieval with no modifications or side effects.
Attacks that exploit this kind of access
Get the current status of a task. Returns status, timestamps, and basic info. It is categorised as a Read tool in the Back-Agent MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Back-Agent MCP Server MCP server in PolicyLayer and add a rule for get-task-status: 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 Back-Agent MCP Server. Nothing to install.
get-task-status 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 get-task-status 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 get-task-status. 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.
get-task-status is provided by the Back-Agent MCP Server MCP server (zuens2020/back-agent-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 →