Fetch a URL and return the content of the page. If you are unable to fetch the page content, might be worth trying to render the JavaScript content.
AI agents call linkup-fetch to retrieve information from Linkup 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 data from web pages without side effects. It reads page content (with optional JavaScript rendering for display purposes) but does not create, modify, delete, or execute arbitrary code. The capability to render JavaScript is for content extraction only, not execution of operations.
From the tool's definition Tool name 'linkup-fetch' and description 'Fetch a URL and return the content of the page' explicitly performs content retrieval with no modification, deletion, or execution of operations on the target system.
Documented attack patterns abuse exactly the kind of access linkup-fetch gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Linkup, and nothing reaches the server without passing your rules. This is the rule we recommend for linkup-fetch:
{
"version": "1",
"default": "deny",
"tools": {
"linkup-fetch": {}
}
}linkup-fetch is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Fetch a URL and return the content of the page. If you are unable to fetch the page content, might be worth trying to render the JavaScript content. It is categorised as a Read tool in the Linkup MCP Server, which means it retrieves data without modifying state.
Register the Linkup MCP server in PolicyLayer and add a rule for linkup-fetch: 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 Linkup. Nothing to install.
linkup-fetch 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 linkup-fetch 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 linkup-fetch. 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.
linkup-fetch is provided by the Linkup MCP server (linkup-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Linkup, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 Linkup tools catalogued and risk-classified — across an index of 43,000+ MCP servers.