resources_access_failure_evidence_lookup
Read resources.access-failure-evidence.lookup through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/resources-access-failure-evidence-lookup.md
What resources_access_failure_evidence_lookup does on Appaloft
AI agents call resources_access_failure_evidence_lookup 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 |
|---|---|---|---|
path | string | — | |
hostname | string | — | |
requestId | string | Yes | |
resourceId | string | — |
Parameters from the server's own tool schema.
Why resources_access_failure_evidence_lookup is rated Low
Even though resources_access_failure_evidence_lookup only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAccepts file system path (path) · Accepts URL/endpoint input (hostname)
Attacks that exploit this kind of access
The rule that runs resources_access_failure_evidence_lookup 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_access_failure_evidence_lookup, this is the rule to start with:
resources_access_failure_evidence_lookup 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_access_failure_evidence_lookup call is checked against it from then on.
Questions about resources_access_failure_evidence_lookup
Read resources.access-failure-evidence.lookup 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_access_failure_evidence_lookup accepts 4 parameters: path, hostname, requestId, resourceId. Required: requestId. 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_access_failure_evidence_lookup: 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_access_failure_evidence_lookup 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_access_failure_evidence_lookup 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_access_failure_evidence_lookup. 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_access_failure_evidence_lookup 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