Get detailed information about a specific Quest property
AI agents call quest_get_property_details to retrieve information from Quest Apartment Hotels 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 and presents existing hotel property information (amenities, pricing, ratings, details) without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with no destructive or side-effect capability.
From the tool's definition Tool name 'quest_get_property_details' and description 'Get detailed information about a specific Quest property' indicate data retrieval with no side effects.
Attacks that exploit this kind of access
Get detailed information about a specific Quest property. It is categorised as a Read tool in the Quest Apartment Hotels MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Quest Apartment Hotels MCP Server MCP server in PolicyLayer and add a rule for quest_get_property_details: 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 Quest Apartment Hotels MCP Server. Nothing to install.
quest_get_property_details 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 quest_get_property_details 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 quest_get_property_details. 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.
quest_get_property_details is provided by the Quest Apartment Hotels MCP Server MCP server (weinerac/quest-mcp-2). 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 →