inspect_untrusted_text
Normalize untrusted text and detect common prompt-injection indicators
This record as markdown: /tools/1999azzar-project-guardian-mcp-server/inspect-untrusted-text.md
What inspect_untrusted_text does on Project Guardian MCP
AI agents call inspect_untrusted_text to retrieve information from Project Guardian MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why inspect_untrusted_text is rated Low
This tool analyzes input text to identify security patterns but does not modify data, execute code, delete information, or trigger external operations. It is a read-only security analysis capability that examines content for malicious patterns. The low severity reflects that misuse would primarily affect analysis accuracy rather than system state or external consequences.
From the tool's definition Tool performs text normalization and detection of prompt-injection indicators; the verb 'inspect' and 'detect' indicate passive analysis without data modification, deletion, or external execution. No side effects mentioned.
Attacks that exploit this kind of access
The rule that runs inspect_untrusted_text safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Project Guardian MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For inspect_untrusted_text, this is the rule to start with:
inspect_untrusted_text 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 Project Guardian MCP, apply this rule, and every inspect_untrusted_text call is checked against it from then on.
Questions about inspect_untrusted_text
Normalize untrusted text and detect common prompt-injection indicators. It is categorised as a Read tool in the Project Guardian MCP MCP Server, which means it retrieves data without modifying state.
Register the Project Guardian MCP server in PolicyLayer and add a rule for inspect_untrusted_text: 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 Project Guardian MCP. Nothing to install.
inspect_untrusted_text 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 inspect_untrusted_text 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 inspect_untrusted_text. 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.
inspect_untrusted_text is provided by the Project Guardian MCP server (1999azzar/project-guardian-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Project Guardian, and thousands of servers like it.
This server
Across the catalogue