Get recent file ingest/tagging events from the monitor. Each event includes: timestamp, event_type (NEW_FILE or RETROACTIVE_TAG), file_name, file_path, md5_hash (ingestid), mime_type (mimeid), size_bytes, and ingest_time. Use this to track which files have been ingested and tagged.
AI agents call get_file_ingest_events 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.
This is a monitoring/audit read operation that only retrieves historical event data from the storage management system. It has no side effects, does not modify state, and does not trigger any operations. Confidence is high because the description clearly indicates data retrieval only ('Get', 'track'). Severity is low because reading event logs poses minimal risk even if accessed by an untrusted agent.
From the tool's definition Tool retrieves and queries recent file ingest/tagging events with fields like timestamp, event_type, file_name, file_path, md5_hash, mime_type, size_bytes, and ingest_time.
Attacks that exploit this kind of access
Get recent file ingest/tagging events from the monitor. Each event includes: timestamp, event_type (NEW_FILE or RETROACTIVE_TAG), file_name, file_path, md5_hash (ingestid), mime_type (mimeid), size_bytes, and ingest_time. Use this to track which files have been ingested and tagged. 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_ingest_events: 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_ingest_events 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_ingest_events 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_ingest_events. 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_ingest_events 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 →