Look up Apple App Store Review Guidelines via greenlight. action
AI agents call fleet_audit_guidelines to retrieve information from Fleet without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves published guidelines (reference data) with zero side effects. It is informational only, fitting the Read category's definition of data retrieval with no side effects. The context of a production management server does not change the benign nature of this lookup operation. Severity is low since misuse would only return irrelevant information without operational impact.
From the tool's definition Tool name 'fleet_audit_guidelines' with description 'Look up Apple App Store Review Guidelines via greenlight. action' indicates retrieval of reference documentation. The verb 'Look up' is a read operation with no modification of data or side effects.
Documented attack patterns abuse exactly the kind of access fleet_audit_guidelines gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Fleet, and nothing reaches the server without passing your rules. This is the rule we recommend for fleet_audit_guidelines:
{
"version": "1",
"default": "deny",
"tools": {
"fleet_audit_guidelines": {}
}
} fleet_audit_guidelines 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.
Look up Apple App Store Review Guidelines via greenlight. action. It is categorised as a Read tool in the Fleet MCP Server, which means it retrieves data without modifying state.
Register the Fleet MCP server in PolicyLayer and add a rule for fleet_audit_guidelines: 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 Fleet. Nothing to install.
fleet_audit_guidelines 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 fleet_audit_guidelines 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 fleet_audit_guidelines. 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.
fleet_audit_guidelines is provided by the Fleet MCP server (wrxck/fleet). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Fleet, 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.
39 Fleet tools catalogued and risk-classified — across an index of 43,000+ MCP servers.