List all the tasks available across all PRDs and User Stories, without task description, only return ID, Title, Ado Id (When Task is linked to ADO), Jira Id (When Task is linked to JIRA), PMO Id(when available), Ado Issue Type(when available), Jira Issue Type(when available)
AI agents call list-all-tasks to retrieve information from Specifai MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists task metadata across documents without creating, modifying, deleting, or executing any operations. It is a straightforward read/query operation with minimal blast radius if misused by an AI agent—at worst, it exposes task enumeration and metadata that appears to be intended for consumption.
From the tool's definition Tool description states it 'List all the tasks' and 'return ID, Title, Ado Id, Jira Id, PMO Id' — purely retrieval operations with no modification, deletion, or execution.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access list-all-tasks gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Specifai MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list-all-tasks:
{
"version": "1",
"default": "deny",
"tools": {
"list-all-tasks": {}
}
}list-all-tasks 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.
List all the tasks available across all PRDs and User Stories, without task description, only return ID, Title, Ado Id (When Task is linked to ADO), Jira Id (When Task is linked to JIRA), PMO Id(when available), Ado Issue Type(when available), Jira Issue Type(when available). It is categorised as a Read tool in the Specifai MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Specifai MCP Server MCP server in PolicyLayer and add a rule for list-all-tasks: 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 Specifai MCP Server. Nothing to install.
list-all-tasks 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 list-all-tasks 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 list-all-tasks. 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.
list-all-tasks is provided by the Specifai MCP Server MCP server (presidio-oss/specifai-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Specifai MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 Specifai MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.