AI agents use add_application_private to create or update resources in Codemagic MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Codemagic MCP Server environment.
The 'add_application' prefix indicates a create operation that modifies system state by adding a new application. This is reversible (applications can be deleted) and falls under Write category. Severity is high because adding an application in a CI/CD system could enable unauthorized builds, artifact access, or resource consumption.
From the tool's definition Tool named 'add_application_private' with no description provided. Based on the 'add_' prefix and the context of a CI/CD API server managing applications, this tool creates or registers a new application in Codemagic.
Documented attack patterns abuse exactly the kind of access add_application_private gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Codemagic MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for add_application_private:
{
"version": "1",
"default": "deny",
"tools": {
"add_application_private": {
"limits": [
{
"counter": "add_application_private_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_application_private 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_application_private. It is categorised as a Write tool in the Codemagic MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Codemagic MCP Server MCP server in PolicyLayer and add a rule for add_application_private: 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 Codemagic MCP Server. Nothing to install.
add_application_private 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_application_private 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_application_private. 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_application_private is provided by the Codemagic MCP Server MCP server (stefanoamorelli/codemagic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Codemagic 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.
16 Codemagic MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.