Get detailed information about a specific attachment including PDF URLs
AI agents call getAttachment to retrieve information from 42 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves attachment metadata and URLs without creating, modifying, deleting, or executing anything. It is a straightforward query operation that returns information about existing resources. The only concern would be if PDF URLs could expose sensitive data, but the retrieval itself is not destructive or risky—the risk lies in what data the URLs point to, which is not the tool's fault.
From the tool's definition Tool name 'getAttachment' and description 'Get detailed information about a specific attachment including PDF URLs' indicate retrieval of existing data with no modification, deletion, or external execution.
Attacks that exploit this kind of access
Get detailed information about a specific attachment including PDF URLs. It is categorised as a Read tool in the 42 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the 42 MCP Server MCP server in PolicyLayer and add a rule for getAttachment: 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 42 MCP Server. Nothing to install.
getAttachment 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 getAttachment 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 getAttachment. 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.
getAttachment is provided by the 42 MCP Server MCP server (smizuoch/42-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →