AI agents use add_source to create or update resources in Automagik Tools — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Automagik Tools environment.
The 'add_' prefix strongly indicates a Write operation that creates or registers something (likely a data source or API endpoint). Without a detailed description, confidence is moderate. Severity is medium because adding a source could enable access to unauthorized APIs or data, but lacks the destructive or financial impact of higher categories. The empty description prevents higher confidence assessment.
From the tool's definition Tool name 'add_source' suggests creating or modifying a data source. The description is empty, limiting specificity. In the context of an API transformation system, 'add' operations typically create or register new resources.
Documented attack patterns abuse exactly the kind of access add_source gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Automagik Tools, and nothing reaches the server without passing your rules. This is the rule we recommend for add_source:
{
"version": "1",
"default": "deny",
"tools": {
"add_source": {
"limits": [
{
"counter": "add_source_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_source 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.
add_source. It is categorised as a Write tool in the Automagik Tools MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Automagik Tools MCP server in PolicyLayer and add a rule for add_source: 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 Automagik Tools. Nothing to install.
add_source 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 add_source 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 add_source. 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.
add_source is provided by the Automagik Tools MCP server (namastexlabs/automagik-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Automagik Tools, 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.
122 Automagik Tools tools catalogued and risk-classified — across an index of 43,000+ MCP servers.