servicenow_metricbase

THE RISK

Low Risk

Why servicenow_metricbase needs a policy

The description is empty and the name alone ('metricbase') suggests metrics/time-series data access, which would typically be Read, but without any description to confirm the tool's behavior, confidence is very low. Defaulting to Other given insufficient information.

From the tool's definition Tool name is 'servicenow_metricbase' with an empty description. No functional details are available.

Documented attack patterns abuse exactly the kind of access servicenow_metricbase gives an agent:

POLICY

How to control servicenow_metricbase

PolicyLayer is an MCP gateway — it sits between your AI agents and Servicenow Api, and nothing reaches the server without passing your rules. This is the rule we recommend for servicenow_metricbase:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "servicenow_metricbase": {
      "limits": [
        {
          "counter": "servicenow_metricbase_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

servicenow_metricbase gets a rate cap, and everything else on the server is denied unless you say otherwise.

Create a free account and register Servicenow Api — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

SET A RULE FOR THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Servicenow Api tools

Execute servicenow_cicd servicenow_cicd Execute servicenow_custom_api servicenow_custom_api Execute servicenow_flows servicenow_flows Write ingest_incidents_to_kg ingest_incidents_to_kg Write servicenow_activity_subscriptions servicenow_activity_subscriptions Write servicenow_attachment servicenow_attachment Write servicenow_change_management servicenow_change_management Write servicenow_cmdb servicenow_cmdb

All 30 Servicenow Api tools →

Other tools on other servers

Android Forensics ADB MCP Server generate_app_analysis_report Ethereum Tools add Math MCP Server complex_analysis_suite Crypto_MCP aes_encrypt

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Tool risk categories → How PolicyLayer classifies MCP tools by what they can do.
MCP tool → What an MCP tool is and how clients discover and call it.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about servicenow_metricbase

What does the servicenow_metricbase tool do? +

servicenow_metricbase. It is categorised as a Other tool in the Servicenow Api MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on servicenow_metricbase? +

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

What risk level is servicenow_metricbase? +

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

Can I rate-limit servicenow_metricbase? +

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

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

servicenow_metricbase is provided by the Servicenow Api MCP server (knuckles-team/servicenow-api). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Servicenow Api tool call.

Start from Servicenow Api, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →