List all available schemes in an Xcode project or workspace
AI agents call list_schemes to retrieve information from App Store Connect without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about Xcode project schemes without modifying, executing, or deleting anything. It is a straightforward read operation similar to 'list' or 'get' operations. The severity is low because accessing scheme metadata poses minimal risk to system integrity or data security.
From the tool's definition Tool name is 'list_schemes' and description states it 'List all available schemes' — a pure query operation with no side effects.
Documented attack patterns abuse exactly the kind of access list_schemes gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and App Store Connect, and nothing reaches the server without passing your rules. This is the rule we recommend for list_schemes:
{
"version": "1",
"default": "deny",
"tools": {
"list_schemes": {}
}
}list_schemes 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.
List all available schemes in an Xcode project or workspace. It is categorised as a Read tool in the App Store Connect MCP Server, which means it retrieves data without modifying state.
Register the App Store Connect MCP server in PolicyLayer and add a rule for list_schemes: 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 App Store Connect. Nothing to install.
list_schemes 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 list_schemes 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 list_schemes. 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.
list_schemes is provided by the App Store Connect MCP server (joshuarileydev/app-store-connect-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from App Store Connect, 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.
27 App Store Connect tools catalogued and risk-classified — across an index of 43,000+ MCP servers.