Geçmiş yolculukları listele
AI agents call yolculuk_gecmisi to retrieve information from Taksi MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and lists past journey records without creating, modifying, or deleting any data. It has no side effects beyond data access. This is a straightforward Read operation with minimal security risk unless the historical data itself contains sensitive information, but the tool's functionality itself is non-destructive and informational.
From the tool's definition Tool name 'yolculuk_gecmisi' and description 'Geçmiş yolculukları listele' (List past journeys) indicate data retrieval with no modification capability. This is a query/list operation returning historical ride information.
Attacks that exploit this kind of access
Geçmiş yolculukları listele. It is categorised as a Read tool in the Taksi MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Taksi MCP Server MCP server in PolicyLayer and add a rule for yolculuk_gecmisi: 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.
yolculuk_gecmisi 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 yolculuk_gecmisi 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 yolculuk_gecmisi. 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.
yolculuk_gecmisi 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 →