manage_certificates · InSite MCP: Risk & Policy

WHAT IT DOES

What manage_certificates does on InSite

AI agents invoke manage_certificates to trigger actions in InSite. 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 manage_certificates needs a policy

Managing certificates in a browser automation context involves installing, trusting, or overriding certificate validation, which can bypass security controls (e.g., accepting self-signed or malicious certs). This constitutes an external security operation with significant blast radius if misused — an agent could disable certificate validation entirely, enabling man-in-the-middle scenarios.

From the tool's definition 'Certificate validation and custom certificate handling' — managing certificates affects TLS/SSL security controls in browser automation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage_certificates Rate-limited

manage_certificates 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": {
    "manage_certificates": {
      "limits": [
        {
          "counter": "manage_certificates_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 InSite, so you can run agents against it safely.

FAQ

Questions about manage_certificates

What does the manage_certificates tool do? +

Certificate validation and custom certificate handling. It is categorised as a Execute tool in the InSite MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on manage_certificates? +

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

What risk level is manage_certificates? +

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

Can I rate-limit manage_certificates? +

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

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

manage_certificates is provided by the InSite MCP server (jowharshamshiri/insite). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.