Get lobbying spend records for a ticker symbol.
AI agents call get_lobbying to retrieve information from Quiver Quantitative 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 and queries existing lobbying expenditure records associated with a ticker symbol. It has no side effects—it neither modifies data, executes code, deletes information, nor commits financial transactions. While the data concerns financial and political activity, the tool itself only enables lookup and analysis of public records, making it a Read operation with low risk when used as intended.
From the tool's definition Tool name 'get_lobbying' and description 'Get lobbying spend records for a ticker symbol' indicate a read-only retrieval operation.
Attacks that exploit this kind of access
Get lobbying spend records for a ticker symbol. It is categorised as a Read tool in the Quiver Quantitative MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Quiver Quantitative MCP Server MCP server in PolicyLayer and add a rule for get_lobbying: 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 Quiver Quantitative MCP Server. Nothing to install.
get_lobbying 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_lobbying 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_lobbying. 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_lobbying is provided by the Quiver Quantitative MCP Server MCP server (nimblebraininc/mcp-quiver). 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 →