getPageSource · PlayMCP Browser Automation Server MCP

WHAT IT DOES

What getPageSource does on PlayMCP Browser Automation Server

AI agents call getPageSource to retrieve information from PlayMCP Browser Automation Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

THE RISK

Low Risk

Why getPageSource needs a policy

This tool retrieves static HTML source without side effects. While HTML source might contain sensitive information depending on page content, the tool itself performs no destructive, executable, or write operations. It falls squarely into the Read category as a data retrieval function.

From the tool's definition Tool description states 'Get the HTML source code of the current page' - a pure retrieval operation with no modification or execution of code. The verb 'Get' and lack of any write/execute/delete semantics confirm this is a read-only operation.

Documented attack patterns abuse exactly the kind of access getPageSource gives an agent:

POLICY

How to control getPageSource

PolicyLayer is an MCP gateway — it sits between your AI agents and PlayMCP Browser Automation Server, and nothing reaches the server without passing your rules. This is the rule we recommend for getPageSource:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "getPageSource": {}
  }
}

getPageSource is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register PlayMCP Browser Automation Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More PlayMCP Browser Automation Server tools

Destructive closeBrowser Close the browser Execute evaluateWithReturn Execute JavaScript code and return the result Execute executeJavaScript Execute arbitrary JavaScript code on the current page and return the result Execute navigate Navigate to a URL Execute waitForSelector Wait for a specific selector to appear on the page Execute waitForText Wait for specific text to appear on the page Execute goForward Navigate forward to the next page in history Execute hover Hover over an element on the page

All 38 PlayMCP Browser Automation Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about getPageSource

What does the getPageSource tool do? +

Get the HTML source code of the current page. It is categorised as a Read tool in the PlayMCP Browser Automation Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getPageSource? +

Register the PlayMCP Browser Automation Server MCP server in PolicyLayer and add a rule for getPageSource: 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 PlayMCP Browser Automation Server. Nothing to install.

What risk level is getPageSource? +

getPageSource is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit getPageSource? +

Yes. Add a rate_limit block to the getPageSource 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.

How do I block getPageSource completely? +

Set action: deny in the PolicyLayer policy for getPageSource. 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.

What MCP server provides getPageSource? +

getPageSource is provided by the PlayMCP Browser Automation Server MCP server (jomon003/playmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every PlayMCP Browser Automation Server tool call.

Start from PlayMCP Browser Automation Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

38 PlayMCP Browser Automation Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.