app_error
AI agents use app_error to create or update resources in Goose App Maker MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Goose App Maker MCP environment.
An AI agent can call app_error faster than any human can review — one bad instruction and it creates or modifies resources in Goose App Maker MCP by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
app_error. It is categorised as a Write tool in the Goose App Maker MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Goose App Maker MCP server in PolicyLayer and add a rule for app_error: 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 Goose App Maker MCP. Nothing to install.
app_error 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 app_error 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 app_error. 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.
app_error is provided by the Goose App Maker MCP server (michaelneale/goose-app-maker-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
app_error is one line of Goose App Maker's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →