Set the active AL app in the workspace
AI agents use set-active-app to create or update resources in AL Object ID Ninja MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AL Object ID Ninja MCP Server environment.
This tool modifies workspace state by changing the active application context. While reversible and not destructive, it is a write operation that changes configuration. Severity is medium rather than high because the blast radius is limited to workspace configuration rather than data deletion or financial impact, though it could affect subsequent ID allocations if the wrong app becomes active.
From the tool's definition Tool name 'set-active-app' and description 'Set the active AL app in the workspace' indicate modification of workspace configuration state. This is a reversible change that affects which application is currently active.
Documented attack patterns abuse exactly the kind of access set-active-app gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AL Object ID Ninja MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for set-active-app:
{
"version": "1",
"default": "deny",
"tools": {
"set-active-app": {
"limits": [
{
"counter": "set-active-app_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} set-active-app 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.
Set the active AL app in the workspace. It is categorised as a Write tool in the AL Object ID Ninja MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AL Object ID Ninja MCP Server MCP server in PolicyLayer and add a rule for set-active-app: 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 AL Object ID Ninja MCP Server. Nothing to install.
set-active-app 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 set-active-app 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 set-active-app. 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.
set-active-app is provided by the AL Object ID Ninja MCP Server MCP server (sshadows/al-objid-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AL Object ID Ninja 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.
26 AL Object ID Ninja MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.