Get detailed profile information for a specific sitter including bio, reviews, services offered, and rates.
AI agents call get_sitter_profile 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 queries and retrieves existing sitter profile data without side effects. It is a straightforward read operation that does not modify, delete, or execute external commands. The information retrieved is profile metadata intended for display/review by the user. Severity is low because misuse would only expose publicly available sitter information without financial, operational, or data integrity risks.
From the tool's definition Tool name 'get_sitter_profile' and description state it 'Get[s] detailed profile information' with 'no creation, modification, or deletion of data mentioned. It retrieves public profile data (bio, reviews, services, rates).
Attacks that exploit this kind of access
Get detailed profile information for a specific sitter including bio, reviews, services offered, and rates. 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_sitter_profile: 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_sitter_profile 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_sitter_profile 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_sitter_profile. 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_sitter_profile 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 →