Medium Risk

resolve_lookup

Resolve an organization slug to its MCP/REST endpoints and trust level — the DNS of professional services. Use this when you know the org_slug and need its API endpoint before calling any other tool. Do NOT use for searching by vertical or location (use resolve.search or registry.search instead)....

Part of the Servicialo MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use resolve_lookup to create or modify resources in Servicialo. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call resolve_lookup repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Servicialo.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

com-servicialo-mcp-server.yaml
tools:
  resolve_lookup:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Servicialo policy for all 10 tools.

Tool Name resolve_lookup
Category Write
Risk Level Medium

View all 10 tools →

Agents calling write-class tools like resolve_lookup have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the resolve_lookup tool do? +

Resolve an organization slug to its MCP/REST endpoints and trust level — the DNS of professional services. Use this when you know the org_slug and need its API endpoint before calling any other tool. Do NOT use for searching by vertical or location (use resolve.search or registry.search instead). Returns: endpoint URLs, trust score (0-100), trust level, and last heartbeat timestamp.. It is categorised as a Write tool in the Servicialo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on resolve_lookup? +

Add a rule in your Intercept YAML policy under the tools section for resolve_lookup. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Servicialo MCP server.

What risk level is resolve_lookup? +

resolve_lookup is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit resolve_lookup? +

Yes. Add a rate_limit block to the resolve_lookup rule in your Intercept 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 resolve_lookup completely? +

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

resolve_lookup is provided by the Servicialo MCP server (@servicialo/mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

Currently onboarding teams running MCP in production.
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.

// REQUEST EARLY ACCESS

We're letting people in as fast as we can.

You're in the queue.

We'll be in touch as soon as we can let you in.