Aktif yolculukta şoförle iletişime geç (ara/mesaj)
AI agents invoke surucu_iletisim to trigger actions in Taksi MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool initiates real-world external operations (phone call or SMS/message) to a driver, which constitutes executing an action with side effects beyond simple data retrieval or writing. It is not destructive or financial, but it does trigger external communication channels, placing it in Execute. Misuse could result in unwanted calls or messages to drivers, hence medium severity.
From the tool's definition Aktif yolculukta şoförle iletişime geç (ara/mesaj) — triggers external communication actions (call/message) to a driver during an active ride
Attacks that exploit this kind of access
Aktif yolculukta şoförle iletişime geç (ara/mesaj). It is categorised as a Execute tool in the Taksi MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Taksi MCP Server MCP server in PolicyLayer and add a rule for surucu_iletisim: 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 Taksi MCP Server. Nothing to install.
surucu_iletisim is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the surucu_iletisim 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 surucu_iletisim. 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.
surucu_iletisim is provided by the Taksi MCP Server MCP server (skynet-base/taksi-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 →