AI agents call get_calibration_history to retrieve information from Msty Admin MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical calibration data from the Msty Studio system. It performs a query-like operation to fetch existing information without creating, modifying, deleting, or executing any actions. The 'get' verb and passive retrieval nature clearly align with the Read category. Severity is low because unauthorized access to calibration history poses minimal immediate risk to system integrity or user safety.
From the tool's definition Tool name 'get_calibration_history' and description 'Get calibration history' indicate a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_calibration_history 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 get_calibration_history:
{
"version": "1",
"default": "deny",
"tools": {
"get_calibration_history": {}
}
}get_calibration_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get calibration history. It is categorised as a Read tool in the Msty Admin MCP MCP Server, which means it retrieves data without modifying state.
Register the Msty Admin MCP server in PolicyLayer and add a rule for get_calibration_history: 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.
get_calibration_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_calibration_history 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 get_calibration_history. 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.
get_calibration_history 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.