Lindy and Dome
Lindy acts in your tools, and rules decide which actions it can take. Lindy switches on every tool an MCP integration lists. Behind a Dome Gateway, that stops mattering: Lindy calls in as a registered agent with its own key, and rules decide which of those tools it may use.
Dome provides a governed gatewayfor Lindy.
A key that's only Lindy's
Lindy authenticates with an agent key minted for it. Revoke that key and Lindy is cut off, while your own agents keep running.
Comment, don't change
Lindy may read Linear issues and comment on them. Creating, editing and closing stay with your team.
Lindy's calls, labeled
Audit files each call under the lindy agent. Filter by it and you see Lindy's work alone.
Lindy on a Gatewayin four steps.
Register Lindy, mint its key, deploy the rules, and then add the Gateway in Lindy as an MCP integration, with the rules doing the scoping.
Register Lindy
Register it with the Linear tools it may reach and the Gateway they sit behind.
shelldome agents register --name lindy \ --tool linear/list_issues \ --tool linear/get_issue \ --tool linear/save_comment \ --gateway ops-gatewayCreate its key
You get back the key and the Gateway's MCP URL, and both go into Lindy and nowhere else.
shelldome agents create-key lindy --name lindy-mcp --gateway ops-gatewayApply the rules
Scope them to the lindy agent. Simulate a create_issue to see it refused, then deploy.
shelldome rules apply lindy-linear.cedar \ --agent lindy --name lindy-linearAdd the Gateway to Lindy
In Lindy, open Integrations, choose Add, then MCP, and paste the MCP URL. Under Advanced, send the key as an Authorization bearer token.
Read issuesand comment.
The permit opens three Linear tools to Lindy. The forbid refuses every other Linear tool, so Lindy can't create, edit or close an issue.
cedar
permit (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when { resource.connection_name == "linear" && ["list_issues", "get_issue", "save_comment"].contains(resource.tool_name)};
forbid (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when { resource.connection_name == "linear" && !["list_issues", "get_issue", "save_comment"].contains(resource.tool_name)};One call,two outcomes.
Switch the caller or the argument and watch the same call decide differently, with every decision landing in audit.
Action
agent lindy · scheduled
linear/save_comment(issueId: "OPS-412", body: "Customer confirmed the fix on their side.")
- Agentlindy is registered and its key is active
- Gatewaylindy may reach ops-gateway
- RuleComments are open to lindy
DecisionAllowed
Bringing it alltogether.
Connecting Lindy to registered tools, models, and identity in Dome completes a governed agent application.
Acting for
Control point
GatewayEvery call decided and audited
RulesGuardsQuotas
Tools
Models
Common questionsabout Lindy.
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
Microsoft Entra ID
Entra access tokens verified on every agent call, so rules read app roles and audit names the person.
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.