create_multistep_check · Pingera MCP Server MCP

WHAT IT DOES

What create_multistep_check does on Pingera MCP Server

AI agents use create_multistep_check to create or update resources in Pingera MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pingera MCP Server environment.

WHY IT NEEDS A POLICY

Why create_multistep_check needs a policy

This tool creates a new monitoring check (multistep variant) in the Pingera monitoring service. Creation of resources is a Write operation—reversible through deletion. While the empty description limits confidence, the naming pattern and sibling context clearly indicate data creation rather than retrieval or deletion.

From the tool's definition Tool name 'create_multistep_check' indicates creation of a monitoring check resource. Sibling tools like 'create_check', 'create_dns_check', 'create_icmp_check' confirm this is a Write operation that creates new monitoring entities.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_multistep_check Rate-limited

create_multistep_check stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_multistep_check": {
      "limits": [
        {
          "counter": "create_multistep_check_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Pingera MCP Server, so you can run agents against it safely.

FAQ

Questions about create_multistep_check

What does the create_multistep_check tool do? +

create_multistep_check. It is categorised as a Write tool in the Pingera MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_multistep_check? +

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

What risk level is create_multistep_check? +

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

Can I rate-limit create_multistep_check? +

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

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

create_multistep_check is provided by the Pingera MCP Server MCP server (pingera/pingera-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.