Get your list of favorited sitters on Rover. Requires being logged in.
AI agents call get_favorites to retrieve information from Rover 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 a user's favorited sitters list—a read-only query operation. It has no capability to modify, delete, execute code, or trigger financial transactions. The 'Requires being logged in' prerequisite is an access control requirement, not an indicator of elevated risk. Misuse would only expose the user's own preferences to the AI agent, presenting minimal blast radius.
From the tool's definition Tool name 'get_favorites' and description 'Get your list of favorited sitters' indicates retrieval of existing data with no modification or side effects.
Attacks that exploit this kind of access
Get your list of favorited sitters on Rover. Requires being logged in. It is categorised as a Read tool in the Rover MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Rover MCP Server MCP server in PolicyLayer and add a rule for get_favorites: 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 Rover MCP Server. Nothing to install.
get_favorites 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_favorites 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_favorites. 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_favorites is provided by the Rover MCP Server MCP server (markswendsen-code/mcp-rover). 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 →