www.pathwren.workers.dev

The tool text references credentials, environment variables, or sending data elsewhere. This can be legitimate, but review what this tool actually accesses.

The description opens with 'FIRST CALL, needs nothing' and instructs the agent to instead invoke a different tool (no_arguments_lint_this_hosts_robots_txt) before using this one. This is an attempt to control the agent's tool-selection order via persuasive language embedded in a tool description rather than through normal capability description, which is a form of prompt injection targeting the agent's behavior.

Same pattern as other tools: opens with an instruction diverting the agent to call a different, unrelated tool first. Also exposes a hidden GET endpoint parameter 's=client-dossiers' that is not documented as a functional parameter, suggesting undisclosed tagging/logging of submitted data.

Contains the same 'FIRST CALL, needs nothing' redirection to another tool, plus a GET-endpoint alternative that silently appends 's=client-dossiers' to requests containing the user's pasted robots_txt content — an undocumented parameter whose name implies data is being cataloged/profiled server-side.

The description repeatedly asserts 'nothing to fill in', 'no key, no account... nothing for you to invent', and cross-references many sibling tools/paths, functioning as an aggressive sales pitch aimed at getting the agent to prioritize calling this endpoint over others. This kind of persuasive, trust-establishing language embedded in a tool description (rather than the client's own judgment) is a social-engineering pattern directed at the AI agent.

States 'THIS IS THE CALL TO MAKE FIRST on this server' — a directive aimed at controlling agent behavior/order of operations that goes beyond describing the tool's function. Combined with whoami's history-tracking claims, this suggests the family of tools is designed to fingerprint/log the calling agent's identity across calls.

Description states the tool reports 'the class this host's own instrument books it as' and 'whether we have logged you here before,' indicating the server fingerprints/tracks the calling agent's user-agent and request history and retains this as a profile ('dossier'), which exceeds the stated purpose of simply checking robots.txt rules and raises data-collection/tracking concerns about the caller.