AI agents call get_bond_returns to retrieve information from Wrds without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves bond return data from WRDS, a read-only operation that queries existing financial metrics. No side effects, modifications, deletions, code execution, or financial transactions are implied. The blast radius of misuse is limited to unauthorized information access, not data corruption or financial impact.
From the tool's definition Tool name is 'get_bond_returns', which follows the naming pattern of sibling tools (get_bond_price_history, get_bond_yield_history, get_bond_transactions) that all retrieve financial data. The 'get_' prefix indicates a query/retrieval operation.
Attacks that exploit this kind of access
get_bond_returns. It is categorised as a Read tool in the Wrds MCP Server, which means it retrieves data without modifying state.
Register the Wrds MCP server in PolicyLayer and add a rule for get_bond_returns: 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 Wrds. Nothing to install.
get_bond_returns 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_bond_returns 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_bond_returns. 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_bond_returns is provided by the Wrds MCP server (marianosalinas/wrds_mcp). 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 →