AI agents call get_leverage_metrics 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 leverage metrics (financial data used for credit and equity analysis) with no side effects. It fits the Read category: queries data, no modifications or operations performed. Severity is medium rather than low because financial data access carries reputational and competitive intelligence risks in finance contexts, but no direct financial or destructive consequences from the tool itself.
From the tool's definition Tool name 'get_leverage_metrics' indicates data retrieval; sibling tools on this server (get_bond_price_history, get_credit_ratings, get_company_overview) are all Read-category queries that retrieve financial data without modification.
Attacks that exploit this kind of access
get_leverage_metrics. 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_leverage_metrics: 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_leverage_metrics 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_leverage_metrics 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_leverage_metrics. 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_leverage_metrics 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 →