get_story_or_task_count
AI agents call get_story_or_task_count to retrieve information from TAPD 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 a count of stories or tasks—a query operation with no side effects. It reads data from the TAPD platform without modifying, executing, or destroying anything. Low severity because counting metadata poses minimal risk even if misused by an agent. Confidence is slightly reduced due to the empty description, but the 'get_' prefix and sibling patterns strongly indicate a safe Read operation.
From the tool's definition Tool name 'get_story_or_task_count' uses the 'get' verb, indicating a retrieval operation. The description is empty, but the naming pattern is consistent with sibling Read tools (e.g., 'get_bug'). No modification, deletion, or execution keywords are present.
Attacks that exploit this kind of access
get_story_or_task_count. It is categorised as a Read tool in the TAPD MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TAPD MCP Server MCP server in PolicyLayer and add a rule for get_story_or_task_count: 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 TAPD MCP Server. Nothing to install.
get_story_or_task_count 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_story_or_task_count 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_story_or_task_count. 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_story_or_task_count is provided by the TAPD MCP Server MCP server (ken19990709/mcp-server-for-tapd). 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 →