get_story
Retrieve detailed information about a specific story bundle by its ID, including the full timeline of related events.
This record as markdown: /tools/com-govbase-govbase/get-story.md
What get_story does on Govbase
AI agents call get_story to retrieve information from Govbase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
bundle_id | string | Yes | Story bundle ID |
Parameters from the server's own tool schema.
Why get_story is rated Low
This tool queries and retrieves narrative/timeline data about stories in the Govbase public policy dataset. No data is created, modified, or deleted. The blast radius of misuse is minimal — an attacker gains only access to information already intended to be public civic data. Severity is low because reading policy stories poses no direct operational, financial, or destructive risk.
From the tool's definition Tool name is 'get_story' and description states 'Retrieve detailed information' — classic Read pattern. The verb 'retrieve' and absence of mutation language (create, delete, modify) confirm no side effects.
Attacks that exploit this kind of access
The rule that runs get_story safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Govbase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_story, this is the rule to start with:
get_story is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Govbase, apply this rule, and every get_story call is checked against it from then on.
Questions about get_story
Retrieve detailed information about a specific story bundle by its ID, including the full timeline of related events. It is categorised as a Read tool in the Govbase MCP Server, which means it retrieves data without modifying state.
get_story accepts 1 parameter: bundle_id. Required: bundle_id. The full parameter table on this page comes from the server's own tool schema.
Register the Govbase MCP server in PolicyLayer and add a rule for get_story: 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 Govbase. Nothing to install.
get_story 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 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. 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 is provided by the Govbase MCP server (https://api.govbase.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Govbase, and thousands of servers like it.
This server
Across the catalogue