Fetches detailed listing info from Turbo.az. Requires listing ID or URL.
AI agents call get_car_details to retrieve information from Turbo Az 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 vehicle listing information based on a listing ID or URL parameter. It has no side effects—it does not create, modify, delete, or execute code. The operation is purely informational, consistent with a Read category tool. Low severity because exposure results only in unauthorized access to publicly-available automotive listing data.
From the tool's definition Tool name 'get_car_details' and description 'Fetches detailed listing info' indicate retrieval of existing data from the Turbo.az marketplace. No modification, deletion, or execution of external operations is described.
Attacks that exploit this kind of access
Fetches detailed listing info from Turbo.az. Requires listing ID or URL. It is categorised as a Read tool in the Turbo Az MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Turbo Az MCP Server MCP server in PolicyLayer and add a rule for get_car_details: 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 Turbo Az MCP Server. Nothing to install.
get_car_details 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_car_details 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_car_details. 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_car_details is provided by the Turbo Az MCP Server MCP server (javidglyv/turboaz-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 →