Get the progress/status transition history for a task
AI agents call get_task_progress_history to retrieve information from MCP Local Database Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query operation to retrieve status transition history for a task. It retrieves or queries data with no side effects—no data is created, modified, deleted, or destroyed. Despite being part of a server with CRUD capabilities, this specific tool is purely a retrieval operation, making it a Read category tool with low risk.
From the tool's definition The tool description explicitly states 'Get the progress/status transition history for a task', indicating it retrieves historical data without modification. The verb 'Get' and the read-only nature of querying history align with the Read category definition.
Attacks that exploit this kind of access
Get the progress/status transition history for a task. It is categorised as a Read tool in the MCP Local Database Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Local Database Server MCP server in PolicyLayer and add a rule for get_task_progress_history: 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 MCP Local Database Server. Nothing to install.
get_task_progress_history 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_progress_history 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_progress_history. 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_progress_history is provided by the MCP Local Database Server MCP server (manojprabhuoffl-ghub/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 →