Write a file inside the Xcode project through the Axint guard path. For Swift files, runs axint.swift.validate and axint.cloud.check immediately, then records .axint/guard/latest.* proof. Use... Use: use only for guarded Xcode-project file writes; outside Xcode, patch normally and validate after....
Risk signalsAccepts file system path (cwd) · Accepts raw HTML/template content (content) · High parameter count (12 properties)
Part of the Axint server.
Free to start. No card required.
AI agents use axint.xcode.write to create or modify resources in Axint. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call axint.xcode.write repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Axint.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"axint.xcode.write": {
"limits": [
{
"counter": "axint.xcode.write_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Axint policy for all 35 tools.
These attack patterns abuse exactly the kind of access axint.xcode.write gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Write a file inside the Xcode project through the Axint guard path. For Swift files, runs axint.swift.validate and axint.cloud.check immediately, then records .axint/guard/latest.* proof. Use... Use: use only for guarded Xcode-project file writes; outside Xcode, patch normally and validate after. Effects: writes the requested file inside cwd, may create dirs, validates Swift, and may write guard/check artifacts.. It is categorised as a Write tool in the Axint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Axint MCP server in PolicyLayer and add a rule for axint.xcode.write: 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 Axint. Nothing to install.
axint.xcode.write 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 axint.xcode.write 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 axint.xcode.write. 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.
axint.xcode.write is provided by the Axint MCP server (@axintai/compiler). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 35 Axint tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.