Get text or HTML content of an element or the entire page.
AI agents call cloak_get_content to retrieve information from CloakBrowser 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 existing page content (text or HTML) without creating, modifying, deleting, or executing actions. It has no side effects beyond information retrieval. Despite the stealth-browser context designed to bypass detection, the tool itself is fundamentally a Read operation.
From the tool's definition Tool name 'cloak_get_content' and description 'Get text or HTML content of an element or the entire page' indicate retrieval/query operations with no modification of data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Get text or HTML content of an element or the entire page. It is categorised as a Read tool in the CloakBrowser MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CloakBrowser MCP Server MCP server in PolicyLayer and add a rule for cloak_get_content: 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 CloakBrowser MCP Server. Nothing to install.
cloak_get_content 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 cloak_get_content 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 cloak_get_content. 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.
cloak_get_content is provided by the CloakBrowser MCP Server MCP server (miwoomiwoo/cloakbrowser-mcp). 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 →