get_stories
List current story bundles tracking ongoing policy issues. Returns a feed of active stories grouping related policies and developments.
This record as markdown: /tools/com-govbase-govbase/get-stories.md
What get_stories does on Govbase
AI agents call get_stories 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 |
|---|---|---|---|
limit | number | — | Number of stories |
Parameters from the server's own tool schema.
Why get_stories is rated Low
This tool retrieves and lists existing public policy story data without creating, modifying, deleting, or executing any operations. It is a read-only query operation with no side effects, consistent with other Read category tools on this server (search_members, search_policies, get_member, get_policy, etc.).
From the tool's definition Tool name 'get_stories' and description 'List current story bundles tracking ongoing policy issues. Returns a feed of active stories' indicate data retrieval with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs get_stories 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_stories, this is the rule to start with:
get_stories 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_stories call is checked against it from then on.
Questions about get_stories
List current story bundles tracking ongoing policy issues. Returns a feed of active stories grouping related policies and developments. It is categorised as a Read tool in the Govbase MCP Server, which means it retrieves data without modifying state.
get_stories accepts 1 parameter: limit. 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_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 Govbase. 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 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