Uploads a finding template from a JSON or TOML string.
AI agents use upload_template to create or update resources in Reptor — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Reptor environment.
This tool creates or modifies template data in the pentest reporting system. While it can alter existing templates, the operation is reversible through updates or deletion, making it a Write operation rather than Destructive.
From the tool's definition Tool description states it "Uploads a finding template from a JSON or TOML string" - this creates or modifies template data in the SysReptor system. The action is reversible (templates can be updated or deleted).
Documented attack patterns abuse exactly the kind of access upload_template gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Reptor, and nothing reaches the server without passing your rules. This is the rule we recommend for upload_template:
{
"version": "1",
"default": "deny",
"tools": {
"upload_template": {
"limits": [
{
"counter": "upload_template_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}upload_template 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.
Uploads a finding template from a JSON or TOML string. It is categorised as a Write tool in the Reptor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Reptor MCP server in PolicyLayer and add a rule for upload_template: 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 Reptor. Nothing to install.
upload_template 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 upload_template 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 upload_template. 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.
upload_template is provided by the Reptor MCP server (slvnlrt/reptor-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Reptor, 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.
7 Reptor tools catalogued and risk-classified — across an index of 43,000+ MCP servers.