find_scope

Find scopes by name or ID substring, optionally narrowed by scope_type.

SERVERAPI-Central SOURCEsecure-ssid/centralmcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/secure-ssid-centralmcp/find-scope.md

WHAT IT DOES

What find_scope does on API-Central

AI agents call find_scope to retrieve information from API-Central without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why find_scope is rated Low

This tool retrieves or queries scope information based on search criteria. The verb 'find' combined with the parameter options (name, ID substring, scope_type filter) describes a read-only lookup operation. There are no side effects, data modifications, code execution, or destructive actions indicated.

From the tool's definition Tool name 'find_scope' and description 'Find scopes by name or ID substring, optionally narrowed by scope_type' indicate a search/query operation with no modification, deletion, or execution of commands.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs find_scope safely

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

find_scope Allowed

find_scope 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": {
    "find_scope": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect API-Central, apply this rule, and every find_scope call is checked against it from then on.

FAQ

Questions about find_scope

What does the find_scope tool do? +

Find scopes by name or ID substring, optionally narrowed by scope_type. It is categorised as a Read tool in the API-Central MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on find_scope? +

Register the API-Central MCP server in PolicyLayer and add a rule for find_scope: 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 API-Central. Nothing to install.

What risk level is find_scope? +

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

Can I rate-limit find_scope? +

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

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

find_scope is provided by the API-Central MCP server (secure-ssid/centralmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on API-Central, and thousands of servers like it.

This server

All 590 API-Central tools →

Across the catalogue

The MCP Attack Database →

Guides

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