Low Risk

schema_analyzer

Analyze a GraphQL introspection result to list queryable operations, mutations, subscriptions, and user-defined types. Filters out built-in GraphQL scalar and meta-types.

Part of the Graphql Rest Bridge server.

schema_analyzer is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE GRAPHQL REST BRIDGE →

Free to start. No card required.

AI agents call schema_analyzer to retrieve information from Graphql Rest Bridge without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though schema_analyzer only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "schema_analyzer": {}
  }
}

See the full Graphql Rest Bridge policy for all 4 tools.

Get this rule live on your own Graphql Rest Bridge server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY GRAPHQL REST BRIDGE →

These attack patterns abuse exactly the kind of access schema_analyzer gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so schema_analyzer only ever does what you allow.

SECURE GRAPHQL REST BRIDGE →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the schema_analyzer tool do? +

Analyze a GraphQL introspection result to list queryable operations, mutations, subscriptions, and user-defined types. Filters out built-in GraphQL scalar and meta-types.. It is categorised as a Read tool in the Graphql Rest Bridge MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on schema_analyzer? +

Register the Graphql Rest Bridge MCP server in PolicyLayer and add a rule for schema_analyzer: 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 Graphql Rest Bridge. Nothing to install.

What risk level is schema_analyzer? +

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

Can I rate-limit schema_analyzer? +

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

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

schema_analyzer is provided by the Graphql Rest Bridge MCP server (https://api.lazy-mac.com/graphql-rest-bridge/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Graphql Rest Bridge tool call.

Deterministic rules across all 4 Graphql Rest Bridge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.