AI agents use set_pickup to create or update resources in Mcp Lyft — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Lyft environment.
set_pickup creates or modifies ride request parameters reversibly (location can be changed before ride confirmation or cancellation). This is a Write operation: it commits data changes to an active ride session without deleting data or executing arbitrary code.
From the tool's definition Tool description states 'Set the pickup location for your ride' — a write operation that modifies ride configuration. Server context describes browser automation for ride-sharing, indicating the tool alters state within a live Lyft session.
Attacks that exploit this kind of access
Set the pickup location for your ride. It is categorised as a Write tool in the Mcp Lyft MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Lyft MCP server in PolicyLayer and add a rule for set_pickup: 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 Mcp Lyft. Nothing to install.
set_pickup is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_pickup 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 set_pickup. 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.
set_pickup is provided by the Mcp Lyft MCP server (markswendsen-code/mcp-lyft). 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 →