Update the status of a specific task
AI agents use speclinter_update_task_status to create or update resources in SpecLinter MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SpecLinter MCP environment.
This tool modifies task status, which is a reversible write operation. It changes task metadata but does not delete data (making it Write rather than Destructive), does not execute external code (not Execute), and does not involve financial transactions (not Financial).
From the tool's definition Tool name 'speclinter_update_task_status' and description 'Update the status of a specific task' indicate modification of existing task data. The verb 'update' confirms reversible state change rather than deletion or irreversible action.
Documented attack patterns abuse exactly the kind of access speclinter_update_task_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SpecLinter MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for speclinter_update_task_status:
{
"version": "1",
"default": "deny",
"tools": {
"speclinter_update_task_status": {
"limits": [
{
"counter": "speclinter_update_task_status_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}speclinter_update_task_status stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update the status of a specific task. It is categorised as a Write tool in the SpecLinter MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SpecLinter MCP server in PolicyLayer and add a rule for speclinter_update_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 SpecLinter MCP. Nothing to install.
speclinter_update_task_status is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the speclinter_update_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 speclinter_update_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.
speclinter_update_task_status is provided by the SpecLinter MCP server (orangebread/speclinter-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 SpecLinter MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 SpecLinter MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.