Get customer leads for specific vehicles or date ranges When to use: Analyze customer interest, correlate inquiries with vehicle performance Lead data: Contact info, inquiry dates, vehicle interest, source tracking Returns: Detailed lead information with vehicle correlation Options: Filter by veh...
AI agents call get_vehicle_leads to retrieve information from StockSpark MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
get_vehicle_leads is a read-only data retrieval tool that queries customer lead records. It retrieves and returns information for analysis (contact info, inquiry dates, vehicle interest) without creating, modifying, or deleting data. While lead data may contain personal information, the tool itself performs no side effects beyond querying an existing database.
From the tool's definition Tool retrieves 'Detailed lead information' and supports querying/filtering by vehicle, date range, and source; returns data without modification.
Attacks that exploit this kind of access
Get customer leads for specific vehicles or date ranges When to use: Analyze customer interest, correlate inquiries with vehicle performance Lead data: Contact info, inquiry dates, vehicle interest, source tracking Returns: Detailed lead information with vehicle correlation Options: Filter by vehicle, date range, lead source Pro tip: Use with vehicle analytics to identify high-interest/low-conversion vehicles Next steps: correlate_leads_performance or update pricing based on lead volume. It is categorised as a Read tool in the StockSpark MCP Server MCP Server, which means it retrieves data without modifying state.
Register the StockSpark MCP Server MCP server in PolicyLayer and add a rule for get_vehicle_leads: 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 StockSpark MCP Server. Nothing to install.
get_vehicle_leads 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_vehicle_leads 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_vehicle_leads. 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_vehicle_leads is provided by the StockSpark MCP Server MCP server (loukach/stockspark-mcp-poc). 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 →