robustness.evaluate_prompt_injection_resistance
Check prompt injection defenses and security measures
This record as markdown: /tools/jrmatherly-mcp-context-forge/robustness.evaluate-prompt-injection-resistance.md
What robustness.evaluate_prompt_injection_resistance does on ContextForge MCP Gateway
AI agents call robustness.evaluate_prompt_injection_resistance to retrieve information from ContextForge MCP Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why robustness.evaluate_prompt_injection_resistance is rated Low
The tool performs a read-only assessment of security posture. 'Check' and 'evaluate' are diagnostic verbs implying observation and reporting of existing conditions, not creation, modification, execution, or deletion of resources. While security-focused, it fits the Read category as it retrieves/queries security metrics and returns findings without triggering external operations or changing system state.
From the tool's definition Tool description states 'Check prompt injection defenses and security measures'—uses passive language ('check') indicating inspection or assessment of existing defenses rather than modification or execution.
Attacks that exploit this kind of access
The rule that runs robustness.evaluate_prompt_injection_resistance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ContextForge MCP Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For robustness.evaluate_prompt_injection_resistance, this is the rule to start with:
robustness.evaluate_prompt_injection_resistance 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 ContextForge MCP Gateway, apply this rule, and every robustness.evaluate_prompt_injection_resistance call is checked against it from then on.
Questions about robustness.evaluate_prompt_injection_resistance
Check prompt injection defenses and security measures. It is categorised as a Read tool in the ContextForge MCP Gateway MCP Server, which means it retrieves data without modifying state.
Register the ContextForge MCP Gateway MCP server in PolicyLayer and add a rule for robustness.evaluate_prompt_injection_resistance: 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 ContextForge MCP Gateway. Nothing to install.
robustness.evaluate_prompt_injection_resistance 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 robustness.evaluate_prompt_injection_resistance 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 robustness.evaluate_prompt_injection_resistance. 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.
robustness.evaluate_prompt_injection_resistance is provided by the ContextForge MCP Gateway MCP server (jrmatherly/mcp-context-forge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ContextForge MCP Gateway, and thousands of servers like it.
This server
Across the catalogue