AI agents call get_monitoring_history to retrieve information from NIST MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries historical monitoring check data. It performs a read-only operation that returns information without creating, modifying, deleting, executing code, or creating financial obligations. The blast radius of misuse is minimal—an agent could review historical data it shouldn't access, but cannot alter security posture or trigger actions. This fits the Read category with low severity.
From the tool's definition The tool is named 'get_monitoring_history' and described as 'Get monitoring check history'. The verb 'Get' and the action of retrieving historical monitoring data indicate a retrieval operation with no data modification or side effects.
Documented attack patterns abuse exactly the kind of access get_monitoring_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and NIST MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_monitoring_history:
{
"version": "1",
"default": "deny",
"tools": {
"get_monitoring_history": {}
}
}get_monitoring_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 monitoring check history. It is categorised as a Read tool in the NIST MCP Server MCP Server, which means it retrieves data without modifying state.
Register the NIST MCP Server MCP server in PolicyLayer and add a rule for get_monitoring_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 NIST MCP Server. Nothing to install.
get_monitoring_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_monitoring_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_monitoring_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_monitoring_history is provided by the NIST MCP Server MCP server (tnicholson/nist-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from NIST MCP Server, 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.
44 NIST MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.