AI agents call speclinter_get_task_status to retrieve information from SpecLinter MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information about a feature or task. It performs no side effects, makes no modifications to data, and triggers no external operations. It is a straightforward read operation that queries the current state of a feature. The blast radius of misuse is minimal—an agent could only retrieve status information it should not have access to, which is a low-severity information disclosure concern.
From the tool's definition Tool name "speclinter_get_task_status" and description "Get the current status of a feature" indicate a query/retrieval operation that returns status information without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access speclinter_get_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_get_task_status:
{
"version": "1",
"default": "deny",
"tools": {
"speclinter_get_task_status": {}
}
}speclinter_get_task_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the current status of a feature\. It is categorised as a Read tool in the SpecLinter MCP MCP Server, which means it retrieves data without modifying state.
Register the SpecLinter MCP server in PolicyLayer and add a rule for speclinter_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 SpecLinter MCP. Nothing to install.
speclinter_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 speclinter_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 speclinter_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.
speclinter_get_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.