gsa_per_diem_lookup
Look up official GSA lodging and meals-and-incidental (M&IE) reimbursement rates for a federal fiscal year and CONUS destination. Provide either a five-digit ZIP, or a two-letter state with an optional city. State-only results are paginated and capped at 25 locations per call. Returns all 12 mont...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/gsa-per-diem-lookup.md
What gsa_per_diem_lookup does on Livedatalink
AI agents call gsa_per_diem_lookup to retrieve information from Livedatalink 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 |
|---|---|---|---|
zip | string | — | Exactly five ZIP digits, preserving leading zeroes. Do not combine with state or city. |
city | string | — | Optional city within state, e.g. 'O'Fallon'. GSA punctuation quirks are normalized safely. |
limit | integer | — | Maximum locations returned; default 10 and hard maximum 25. |
state | string | — | Two-letter code for a contiguous state or DC. Required with city; omit when using zip. |
offset | integer | — | Locations to skip for state-result pagination; default 0. |
fiscal_year | integer | Yes | Four-digit federal fiscal year. GSA generally publishes the current three fiscal years. |
Parameters from the server's own tool schema.
Why gsa_per_diem_lookup is rated Low
Even though gsa_per_diem_lookup only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs gsa_per_diem_lookup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gsa_per_diem_lookup, this is the rule to start with:
gsa_per_diem_lookup 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 Livedatalink, apply this rule, and every gsa_per_diem_lookup call is checked against it from then on.
Questions about gsa_per_diem_lookup
Look up official GSA lodging and meals-and-incidental (M&IE) reimbursement rates for a federal fiscal year and CONUS destination. Provide either a five-digit ZIP, or a two-letter state with an optional city. State-only results are paginated and capped at 25 locations per call. Returns all 12 monthly lodging limits, the daily M&IE limit, locality/county coverage, and official source metadata. GSA fiscal years run October 1 through September 30; Alaska, Hawaii, territories, and foreign locations use other federal rate sources. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
gsa_per_diem_lookup accepts 6 parameters: zip, city, limit, state, offset, fiscal_year. Required: fiscal_year. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for gsa_per_diem_lookup: 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 Livedatalink. Nothing to install.
gsa_per_diem_lookup 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 gsa_per_diem_lookup 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 gsa_per_diem_lookup. 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.
gsa_per_diem_lookup is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue