List all available signals for a vehicle with their current values and status. Use this to discover which signals a vehicle supports before calling get_signal.
AI agents call get_signals to retrieve information from Smartcar 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 telemetry data without modifying, deleting, or executing any commands. It is a discovery/listing operation that allows agents to see available signals before querying specific ones. The blast radius of misuse is minimal—an attacker gains visibility into vehicle capabilities but cannot control, delete, or financially impact the vehicle or user.
From the tool's definition Tool name is 'get_signals' and description explicitly states it 'List all available signals for a vehicle with their current values and status' - a purely informational query operation with no side effects.
Attacks that exploit this kind of access
List all available signals for a vehicle with their current values and status. Use this to discover which signals a vehicle supports before calling get_signal. It is categorised as a Read tool in the Smartcar MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Smartcar MCP Server MCP server in PolicyLayer and add a rule for get_signals: 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 Smartcar MCP Server. Nothing to install.
get_signals 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_signals 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_signals. 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_signals is provided by the Smartcar MCP Server MCP server (thachdosc/smartcar-mcp-test). 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 →