Get recent Resource Monitor threshold events (CPU/RAM/IO spikes over time).
AI agents call get_resource_history to retrieve information from Synology 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 historical resource monitoring data from the Synology NAS without modifying, deleting, or executing any operations. It is a passive data retrieval mechanism for observing system performance metrics. The blast radius if misused is minimal—an attacker could only gain visibility into historical resource usage patterns, not manipulate system state or access sensitive user data directly.
From the tool's definition Tool name 'get_resource_history' and description 'Get recent Resource Monitor threshold events' indicate a query/retrieval operation with no modifications.
Attacks that exploit this kind of access
Get recent Resource Monitor threshold events (CPU/RAM/IO spikes over time). It is categorised as a Read tool in the Synology MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Synology MCP Server MCP server in PolicyLayer and add a rule for get_resource_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 Synology MCP Server. Nothing to install.
get_resource_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_resource_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_resource_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_resource_history is provided by the Synology MCP Server MCP server (rafalr100/synology-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →