Get current status of the automatic file monitoring service. The monitor runs continuously with the MCP server, watching Hammerspace NFS mounts for new files and auto-tagging them with ingestid (MD5) and mimeid (MIME type). Returns: running state, watched paths, pending events, known files count,...
AI agents call get_file_monitor_status to retrieve information from Hammerspace Storage Management MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
get_file_monitor_status purely retrieves the current operational state and metrics of the file monitoring service. It performs no writes, deletions, code execution, or financial operations. The tool only observes and reports status information, making it a straightforward Read category tool with low severity since misuse would only expose monitoring metadata about the storage system.
From the tool's definition Tool description states it 'Get[s] current status' and 'Returns: running state, watched paths, pending events, known files count, CPU usage, and last batch time.' These are all read-only queries with no modifications, side effects, or state changes.
Attacks that exploit this kind of access
Get current status of the automatic file monitoring service. The monitor runs continuously with the MCP server, watching Hammerspace NFS mounts for new files and auto-tagging them with ingestid (MD5) and mimeid (MIME type). Returns: running state, watched paths, pending events, known files count, CPU usage, and last batch time. It is categorised as a Read tool in the Hammerspace Storage Management MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Hammerspace Storage Management MCP Server MCP server in PolicyLayer and add a rule for get_file_monitor_status: 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 Hammerspace Storage Management MCP Server. Nothing to install.
get_file_monitor_status 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_file_monitor_status 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_file_monitor_status. 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_file_monitor_status is provided by the Hammerspace Storage Management MCP Server MCP server (mbloomhammerspace/mcp-1.5-main). 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 →