get_stories
AI agents call get_stories 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.
The tool retrieves story data from VersionOne for querying purposes. The 'get_' prefix, absence of mutation language, and context of sibling read-only query tools all indicate this is a Read operation with no data modification, deletion, or external execution. Low severity due to information-only nature and typical project management data scope.
From the tool's definition Tool name 'get_stories' combined with server description that "Enables AI assistants to query VersionOne for stories" and sibling tools named 'get_feature_details', 'get_features', 'get_story_details' all follow a retrieval/query pattern.
Attacks that exploit this kind of access
get_stories. 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_stories: 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_stories 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 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. 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 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 →