Get detailed information about a specific story by ID.
AI agents call get_story_details to retrieve information from VersionOne 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 queries data from VersionOne without creating, modifying, deleting, or executing any operations. It is a straightforward data retrieval function that fits the 'Read' category. The severity is low because misuse only risks exposing existing project management data, not causing harm or irreversible changes.
From the tool's definition Tool name 'get_story_details' and description 'Get detailed information about a specific story by ID' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get detailed information about a specific story by ID. It is categorised as a Read tool in the VersionOne MCP Server MCP Server, which means it retrieves data without modifying state.
Register the VersionOne MCP Server MCP server in PolicyLayer and add a rule for get_story_details: 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 VersionOne MCP Server. Nothing to install.
get_story_details 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_details 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_details. 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_details is provided by the VersionOne MCP Server MCP server (quantiser/mcp-server). 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 →