Announcing Dome Managed Agents.

Try it now

Linkup MCP server and Dome

Give agents the web while keeping your project names off it. Linkup's remote MCP server searches the web, fetches pages and runs long research jobs. A fetch is where an agent picks its own sources. Put Linkup behind Dome, and a rule holds every fetch to the sources you trust, such as sec.gov and eur-lex.

Dome provides a governed gatewayfor Linkup.

Sources you trust, and no others

A rule reads the url of linkup-fetch, so a regulation on eur-lex comes back and a paste site is refused.

Research jobs off by default

linkup-research and linkup-get-research stay closed. Open them for the one agent that needs a long-running job.

Search without the codename

A forbid refuses any search that names Project Halcyon, so Linkup never receives it. A guard catches personal data in any argument.

Linkup behind the Gatewayin four steps.

Add Linkup's server, sync its four tools, guard outbound arguments, then deploy the source list.
  1. Add the Linkup MCP server

    Every agent shares one Linkup API key, held by Dome and sent as a Bearer token.

    shell
    dome tools add --name linkup \  --url https://mcp.linkup.so/mcp \  --auth-method api-key \  --credential-type shared \  --authorization "Bearer $LINKUP_API_KEY" \  --gateway prod-gateway
  2. Sync the catalog

    Sync lists linkup-search, linkup-fetch, linkup-research and linkup-get-research. Calls fail until the catalog has them.

    shell
    dome tools catalog sync linkup
  3. Block personal data in arguments

    Request filters see each argument before Linkup does, and a match ends the call there.

    shell
    cat > query-leak.json <<'EOF'{"json":{"components":[{"fieldActions":[{  "matcher":{"contentMatchers":[{"ssn":{}},{"creditCard":{"requireLuhn":true}},{"email":{}}]},  "action":"FILTER_ACTION_BLOCK"}]}]}}EOFdome guards filters create query-leak --config-from query-leak.jsondome tools guards filters set linkup --direction request --filters query-leak
  4. Apply the rules

    The source list is scoped to policy-analyst. Simulate a fetch from each source, then deploy.

    shell
    dome rules apply linkup-sources.cedar --agent policy-analyst --name linkup-sources

Search anything,fetch from two sources.

The permit opens search and fetch. Forbids close the research tools, refuse any search that names Project Halcyon and refuse a fetch outside sec.gov and eur-lex.
cedar
permit (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when {  resource.connection_name == "linkup" &&  ["linkup-search", "linkup-fetch"].contains(resource.tool_name)};
forbid (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when {  resource.connection_name == "linkup" &&  !["linkup-search", "linkup-fetch"].contains(resource.tool_name)};
forbid (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when {  resource.connection_name == "linkup" &&  resource.tool_name == "linkup-search" &&  resource has arguments &&  resource.arguments has query &&  resource.arguments.query like "*Halcyon*"};
forbid (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when {  resource.connection_name == "linkup" &&  resource.tool_name == "linkup-fetch" &&  !(resource has arguments &&    resource.arguments has url &&    (resource.arguments.url like "https://www.sec.gov/*" ||     resource.arguments.url like "https://eur-lex.europa.eu/*"))};

One call,two outcomes.

Switch the caller or the argument and watch the same call decide differently, with every decision landing in audit.

Source

agent policy-analyst · acting as a.novak
linkup/linkup-fetch(url: "https://eur-lex.europa.eu/eli/reg/2024/1689/oj")
  1. Agentpolicy-analyst is registered and active
  2. Callera.novak verified through Okta
  3. RuleFetches from eur-lex.europa.eu are allowed
DecisionAllowed

Three agentson Linkup.

Each one searches the open web. Only one fetches pages, and only from the sources it's given.

policy-analyst

Read the regulation

Fetches the text of EU and SEC rules and drafts summaries for counsel, and is refused on any other source.

news-briefer

Brief the team each morning

Searches the news for named accounts and writes a short brief before the day starts.

deal-scout

Scout acquisition targets

Looks for companies that fit a thesis by sector, size and region. A search that names the deal is refused at the Gateway.

Bringing it alltogether.

Connecting Linkup to registered agents, models, and identity in Dome completes a governed agent application.
Dome

Control point

GatewayEvery call decided and audited
RulesGuardsQuotas

Tools

LinkupAgent service

Common questionsabout Linkup.

Does Linkup have a remote MCP server?
Yes. It runs at mcp.linkup.so/mcp, and Dome adds it with your Linkup API key.
Can I keep a Linkup agent to approved sources?
Yes. The rule reads the url of every linkup-fetch. Pages on sec.gov and eur-lex come back, and anything else is refused.
Can I keep internal project names out of Linkup searches?
Yes. A forbid on the query argument refuses a search that names the project, and Linkup never receives the query.

More of whatDome works with.

Model

Claude Fable

Fable 5.1 from Anthropic and Amazon Bedrock in one failover pool, open to one group and capped by quota.
Provider

Anthropic

The Claude API behind the Model Broker: the key held in Dome, every call authorized, metered and audited.
MCP server

GitHub

The GitHub MCP server behind the Tool Gateway, with rules that decide each call on its owner and repository.
Identity

Okta

Okta tokens verified on every agent call, so rules and audit name the person each agent acted for.
Runtime

LangGraph

LangGraph agents with their model calls on the Model Broker and their MCP tools on the Tool Gateway.
Client

Claude Code

Claude Code on a Dome Gateway with per-developer sign-in, rules on every tool call, and audit by name.

Talk with ourFDE team.

Or start free, and register your first agent in minutes. Connect it through a gateway, give it rules, and see every call it makes in one audit trail.

Talk with our FDE team

Our engineers design, build and run governed agents for the part of your business you want to change. You see what they deliver.

Agent services: web, research, payments, voice and sandboxes

Web actions, research, payments, phone calls and code execution are where agents reach past your walls. Put each service behind the Gateway, and every call is authorized, metered and audited.

Every agent you run, under one system of control.