get_us_inflation
AI agents call get_us_inflation to retrieve information from WorldBank GDP & Employment MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves US inflation data from the WorldBank API or similar economic data source. It has no side effects—it only fetches and returns existing data without modifying, deleting, or executing code. It poses minimal risk to an AI agent's ability to misuse it, as inflation data is public information with no destructive or financial transaction capability.
From the tool's definition Tool name 'get_us_inflation' and server context (WorldBank GDP & Employment MCP Server that retrieves economic and labor market data) indicate this is a data retrieval function.
Attacks that exploit this kind of access
get_us_inflation. It is categorised as a Read tool in the WorldBank GDP & Employment MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WorldBank GDP & Employment MCP Server MCP server in PolicyLayer and add a rule for get_us_inflation: 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 WorldBank GDP & Employment MCP Server. Nothing to install.
get_us_inflation 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_us_inflation 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_us_inflation. 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_us_inflation is provided by the WorldBank GDP & Employment MCP Server MCP server (moderator11/mcpserver-gdp). 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 →