Upload SharpHound/AzureHound collection files to BloodHound CE for ingest. Accepts .zip (SharpHound ZIP archive) or .json (individual collection file). info_type options: upload - full workflow for a single file: start -> upload -> end (requires: file_path) start_job - start a new upload job, ret...
AI agents use file_upload to create or update resources in BloodHound MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BloodHound MCP Server environment.
This tool creates or modifies data within BloodHound by ingesting Active Directory collection files. While the ingest process is reversible (files can be removed from BloodHound), the act of uploading and processing files represents data creation/modification.
From the tool's definition Tool description explicitly states 'Upload SharpHound/AzureHound collection files to BloodHound CE for ingest.' The info_type options include 'upload' (full workflow) and 'upload_to_job' with file_path parameters, indicating data is being created or added to…
Documented attack patterns abuse exactly the kind of access file_upload gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and BloodHound MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for file_upload:
{
"version": "1",
"default": "deny",
"tools": {
"file_upload": {
"limits": [
{
"counter": "file_upload_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}file_upload stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Upload SharpHound/AzureHound collection files to BloodHound CE for ingest. Accepts .zip (SharpHound ZIP archive) or .json (individual collection file). info_type options: upload - full workflow for a single file: start -> upload -> end (requires: file_path) start_job - start a new upload job, returns job_id for multi-file uploads upload_to_job - upload a file to an existing job (requires: job_id, file_path) end_job - finalize an upload job and trigger ingest (requires: job_id) Args: info_type: operation to perform (default: upload) file_path: absolute path to collection file (.zip or .json) job_id: upload job ID (required for upload_to_job and end_job). It is categorised as a Write tool in the BloodHound MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the BloodHound MCP Server MCP server in PolicyLayer and add a rule for file_upload: 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 BloodHound MCP Server. Nothing to install.
file_upload is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the file_upload 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 file_upload. 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.
file_upload is provided by the BloodHound MCP Server MCP server (mwnickerson/bloodhound_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from BloodHound 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.
13 BloodHound MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.