run_visibility_check · MCP Starter for Puch AI MCP

WHAT IT DOES

What run_visibility_check does on MCP Starter for Puch AI

AI agents invoke run_visibility_check to trigger actions in MCP Starter for Puch AI. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why run_visibility_check needs a policy

This tool executes a visibility check across multiple LLM platforms, which is an operation that triggers external system interactions and produces effects based on the query provided. While it is read-oriented in outcome (retrieving visibility data), the mechanism involves executing a check process across external systems, making it Execute rather than Read.

From the tool's definition 'Run visibility check for a specific query across LLM platforms' indicates execution of a check operation that queries external platforms and returns results dependent on the input query parameter.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_visibility_check Rate-limited

run_visibility_check stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_visibility_check": {
      "limits": [
        {
          "counter": "run_visibility_check_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about run_visibility_check

What does the run_visibility_check tool do? +

Run visibility check for a specific query across LLM platforms. It is categorised as a Execute tool in the MCP Starter for Puch AI MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_visibility_check? +

Register the MCP Starter for Puch AI MCP server in PolicyLayer and add a rule for run_visibility_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 MCP Starter for Puch AI. Nothing to install.

What risk level is run_visibility_check? +

run_visibility_check is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_visibility_check? +

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

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

run_visibility_check is provided by the MCP Starter for Puch AI MCP server (kulraj69/mcp-llm). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.