get_policy
Retrieve detailed information about a specific U.S. federal policy by its ID (e.g., "bill-119-hr-22" or "eo-2025-1234").
This record as markdown: /tools/com-govbase-govbase/get-policy.md
What get_policy does on Govbase
AI agents call get_policy 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 |
|---|---|---|---|
policy_id | string | Yes | Policy ID (e.g., "bill-119-hr-22" or "eo-2025-1234") |
Parameters from the server's own tool schema.
Why get_policy is rated Low
This tool queries and returns existing public federal policy data by ID. It has no side effects, cannot modify or delete records, cannot execute code or external operations, and involves no financial transactions. The data retrieved is civic information already public. This is a straightforward read-only retrieval operation with minimal risk.
From the tool's definition Tool name 'get_policy' and description 'Retrieve detailed information about a specific U.S. federal policy' indicate a data retrieval operation with no modification, creation, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs get_policy 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_policy, this is the rule to start with:
get_policy 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_policy call is checked against it from then on.
Questions about get_policy
Retrieve detailed information about a specific U.S. federal policy by its ID (e.g., "bill-119-hr-22" or "eo-2025-1234"). It is categorised as a Read tool in the Govbase MCP Server, which means it retrieves data without modifying state.
get_policy accepts 1 parameter: policy_id. Required: policy_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_policy: 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_policy 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_policy 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_policy. 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_policy 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