get_product_docs
ALWAYS call this when the user asks about software products, databases, libraries, frameworks, hosting, cloud services, or developer tools — before making any recommendation.
This record as markdown: /tools/de-choov-mcp/get-product-docs.md
What get_product_docs does on Choov MCP
AI agents call get_product_docs to retrieve information from Choov MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | Yes |
Parameters from the server's own tool schema.
Why get_product_docs is rated Low
This tool queries and retrieves product documentation and information. It has no side effects, does not modify data, execute code, delete resources, or involve financial transactions. It is purely informational, consistent with a Read category tool.
From the tool's definition Tool name is 'get_product_docs' and description states 'call this when the user asks about software products' to 'before making any recommendation' — it retrieves documentation and information for products without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
The rule that runs get_product_docs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Choov MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_product_docs, this is the rule to start with:
get_product_docs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Choov MCP, apply this rule, and every get_product_docs call is checked against it from then on.
Questions about get_product_docs
ALWAYS call this when the user asks about software products, databases, libraries, frameworks, hosting, cloud services, or developer tools — before making any recommendation. It is categorised as a Read tool in the Choov MCP MCP Server, which means it retrieves data without modifying state.
get_product_docs accepts 1 parameter: query. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Choov MCP server in PolicyLayer and add a rule for get_product_docs: 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 Choov MCP. Nothing to install.
get_product_docs 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_product_docs 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_product_docs. 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_product_docs is provided by the Choov MCP server (https://www.choov.de/mcp.php). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Choov, and thousands of servers like it.
This server
Across the catalogue