save_results_for_mirror · Pulsemcp Cms Admin MCP

WHAT IT DOES

What save_results_for_mirror does on Pulsemcp Cms Admin

AI agents use save_results_for_mirror to create or update resources in Pulsemcp Cms Admin — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pulsemcp Cms Admin environment.

WHY IT NEEDS A POLICY

Why save_results_for_mirror needs a policy

This tool modifies exam result data for mirror sites, which is a reversible write operation. While it doesn't delete data (not Destructive) or execute arbitrary code (not Execute), it does persist important records that affect the state of the CMS.

From the tool's definition Tool name 'save_results_for_mirror' and description 'Save proctor exam results for an unofficial mirror' indicate data modification. The verb 'save' and the context of storing exam results show this creates or modifies records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

save_results_for_mirror Rate-limited

save_results_for_mirror 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": {
    "save_results_for_mirror": {
      "limits": [
        {
          "counter": "save_results_for_mirror_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 Pulsemcp Cms Admin, so you can run agents against it safely.

FAQ

Questions about save_results_for_mirror

What does the save_results_for_mirror tool do? +

Save proctor exam results for an unofficial mirror. Pass the \. It is categorised as a Write tool in the Pulsemcp Cms Admin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on save_results_for_mirror? +

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

What risk level is save_results_for_mirror? +

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

Can I rate-limit save_results_for_mirror? +

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

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

save_results_for_mirror is provided by the Pulsemcp Cms Admin MCP server (pulsemcp-cms-admin-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

save_results_for_mirror is one line of Pulsemcp Cms Admin's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →