AI agents invoke run_calibration_test to trigger actions in Msty Admin MCP. 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.
This tool triggers an external operation (a calibration test) on a model, which is a computational/operational action that modifies system state and whose outcome depends on supplied arguments. This fits the Execute category—it runs a process rather than simply reading data (Read) or creating reversible data structures (Write).
From the tool's definition Tool name 'run_calibration_test' indicates execution of a test process on a model. The verb 'run' combined with 'test' describes invoking an operation whose effects depend on the model and test parameters provided.
Documented attack patterns abuse exactly the kind of access run_calibration_test gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Msty Admin MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for run_calibration_test:
{
"version": "1",
"default": "deny",
"tools": {
"run_calibration_test": {
"limits": [
{
"counter": "run_calibration_test_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_calibration_test 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.
Free to start. No card required.
Run calibration test on a model. It is categorised as a Execute tool in the Msty Admin MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Msty Admin MCP server in PolicyLayer and add a rule for run_calibration_test: 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 Msty Admin MCP. Nothing to install.
run_calibration_test is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_calibration_test 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.
Set action: deny in the PolicyLayer policy for run_calibration_test. 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.
run_calibration_test is provided by the Msty Admin MCP server (m-pineapple/msty-admin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Msty Admin MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
36 Msty Admin MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.