AI agents call screen_issuers 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.
The tool appears to be a screening/filtering tool for financial issuers within the WRDS data platform. Screening is a read operation that retrieves matching records based on criteria without creating, modifying, or deleting data. The server's focus on 'query' and 'analysis' alongside the pattern of all sibling tools being read-only retrieval operations strongly suggests this is a data query tool.
From the tool's definition Tool name 'screen_issuers' suggests filtering or querying issuer data. The server context describes tools that 'query' financial data and enable users to 'query bond history, credit ratings, financial metrics' without modification.
Attacks that exploit this kind of access
screen_issuers. 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 screen_issuers: 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.
screen_issuers 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 screen_issuers 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 screen_issuers. 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.
screen_issuers 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 →