Read the full content of a specific documentation file to get code examples and detailed API usage.
AI agents call read_doc to retrieve information from Ohos Mcp Unofficial without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries documentation content without side effects. It enables reading, searching, and analyzing existing documentation files—classic Read category behavior. No data creation, modification, deletion, code execution, or financial operations are possible. The low severity reflects minimal risk from misuse, as documentation retrieval alone cannot damage systems or data.
From the tool's definition Tool name 'read_doc' and description 'Read the full content of a specific documentation file' explicitly indicates data retrieval with no modification or execution capability.
Attacks that exploit this kind of access
Read the full content of a specific documentation file to get code examples and detailed API usage. It is categorised as a Read tool in the Ohos Mcp Unofficial MCP Server, which means it retrieves data without modifying state.
Register the Ohos Mcp Unofficial MCP server in PolicyLayer and add a rule for read_doc: 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 Ohos Mcp Unofficial. Nothing to install.
read_doc 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 read_doc 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 read_doc. 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.
read_doc is provided by the Ohos Mcp Unofficial MCP server (megaacheyounes/ohos-mcp-unofficial). 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 →