safety.evaluate_refusal_appropriateness
Check when system appropriately refuses potentially harmful requests
This record as markdown: /tools/jrmatherly-mcp-context-forge/safety.evaluate-refusal-appropriateness.md
What safety.evaluate_refusal_appropriateness does on ContextForge MCP Gateway
AI agents call safety.evaluate_refusal_appropriateness 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 safety.evaluate_refusal_appropriateness is rated Low
This tool performs an assessment or audit of refusal decisions—a read-only introspection capability. It retrieves or analyzes information about whether the system has correctly refused a harmful request, with no side effects, data modification, code execution, or destruction.
From the tool's definition Tool name 'evaluate_refusal_appropriateness' and description 'Check when system appropriately refuses potentially harmful requests' indicate inspection/analysis of refusal behavior without modifying, executing, or destroying anything.
Attacks that exploit this kind of access
The rule that runs safety.evaluate_refusal_appropriateness 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 safety.evaluate_refusal_appropriateness, this is the rule to start with:
safety.evaluate_refusal_appropriateness 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 safety.evaluate_refusal_appropriateness call is checked against it from then on.
Questions about safety.evaluate_refusal_appropriateness
Check when system appropriately refuses potentially harmful requests. 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 safety.evaluate_refusal_appropriateness: 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.
safety.evaluate_refusal_appropriateness 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 safety.evaluate_refusal_appropriateness 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 safety.evaluate_refusal_appropriateness. 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.
safety.evaluate_refusal_appropriateness 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