Check if an AL app is authorized
AI agents call check-authorization to retrieve information from AL Object ID Ninja MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that retrieves authorization status information. It has no side effects, does not create, modify, or delete data, and does not execute code or trigger external operations. The blast radius of misuse is minimal—an attacker could only learn whether an app is authorized, which is informational in nature. This fits the 'Read' category as a status check/query operation.
From the tool's definition The tool name 'check-authorization' and description 'Check if an AL app is authorized' indicate a query operation that verifies authorization status without modifying any data or triggering external operations.
Documented attack patterns abuse exactly the kind of access check-authorization 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 check-authorization:
{
"version": "1",
"default": "deny",
"tools": {
"check-authorization": {}
}
} check-authorization is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check if an AL app is authorized. It is categorised as a Read tool in the AL Object ID Ninja MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AL Object ID Ninja MCP Server MCP server in PolicyLayer and add a rule for check-authorization: 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.
check-authorization is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check-authorization 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 check-authorization. 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.
check-authorization 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.