resources_proxy_configuration_preview
Read resources.proxy-configuration.preview through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/resources-proxy-configuration-preview.md
What resources_proxy_configuration_preview does on Appaloft
AI agents call resources_proxy_configuration_preview to retrieve information from Appaloft without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
resourceId | string | Yes | |
routeScope | string | — | |
deploymentId | string | — | |
includeDiagnostics | object | — |
Parameters from the server's own tool schema.
Why resources_proxy_configuration_preview is rated Low
This tool retrieves or previews proxy configuration data through the application operation catalog. The explicit use of "Read" in the description and the "preview" operation confirm this is a query/retrieval operation with no destructive, executable, or financial implications. Severity is low as configuration preview operations typically have minimal blast radius.
From the tool's definition Tool description states "Read resources.proxy-configuration.preview"; the verb "Read" and "preview" indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs resources_proxy_configuration_preview safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For resources_proxy_configuration_preview, this is the rule to start with:
resources_proxy_configuration_preview is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Appaloft, apply this rule, and every resources_proxy_configuration_preview call is checked against it from then on.
Questions about resources_proxy_configuration_preview
Read resources.proxy-configuration.preview through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Read tool in the Appaloft MCP Server, which means it retrieves data without modifying state.
resources_proxy_configuration_preview accepts 4 parameters: resourceId, routeScope, deploymentId, includeDiagnostics. Required: resourceId. The full parameter table on this page comes from the server's own tool schema.
Register the Appaloft MCP server in PolicyLayer and add a rule for resources_proxy_configuration_preview: 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 Appaloft. Nothing to install.
resources_proxy_configuration_preview 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 resources_proxy_configuration_preview 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 resources_proxy_configuration_preview. 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.
resources_proxy_configuration_preview is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Appaloft, and thousands of servers like it.
This server
Across the catalogue