get_stories_or_tasks
AI agents call get_stories_or_tasks 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.
The 'get_' prefix strongly suggests a read operation that retrieves existing stories or tasks from the TAPD platform. No modification, deletion, or execution of external operations is implied. The tool fits the Read category pattern of querying data with no side effects. Confidence is slightly reduced due to empty description, but the naming pattern is clear and consistent with standard CRUD naming conventions.
From the tool's definition Tool name 'get_stories_or_tasks' uses the 'get' verb indicating retrieval. Description is empty but naming convention and sibling context (TAPD agile project management) indicate querying/fetching data without modification.
Attacks that exploit this kind of access
get_stories_or_tasks. 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_stories_or_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 TAPD MCP Server. Nothing to install.
get_stories_or_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 get_stories_or_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 get_stories_or_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.
get_stories_or_tasks 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 →