get_url

Devuelve la URL actual del browser.

SERVER4bis Relay Showcase SOURCEFourBis/4bis.relay-showcase

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/4bis-relay-showcase/get-url.md

WHAT IT DOES

What get_url does on 4bis Relay Showcase

AI agents call get_url to retrieve information from 4bis Relay Showcase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_url is rated Low

Returns current browser URL; read-only information retrieval with no modifications or side effects.

From the tool's definition Devuelve la URL actual del browser; retrieves current state without side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_url safely

PolicyLayer is an MCP gateway: it sits between your AI agents and 4bis Relay Showcase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_url, this is the rule to start with:

get_url Allowed

get_url is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 4bis Relay Showcase, apply this rule, and every get_url call is checked against it from then on.

FAQ

Questions about get_url

What does the get_url tool do? +

Devuelve la URL actual del browser. It is categorised as a Read tool in the 4bis Relay Showcase MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_url? +

Register the 4bis Relay Showcase MCP server in PolicyLayer and add a rule for get_url: 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 4bis Relay Showcase. Nothing to install.

What risk level is get_url? +

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

Can I rate-limit get_url? +

Yes. Add a rate_limit block to the get_url 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 get_url completely? +

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

get_url is provided by the 4bis Relay Showcase MCP server (FourBis/4bis.relay-showcase). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on 4bis Relay Showcase, and thousands of servers like it.

This server

All 16 4bis Relay Showcase tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →