robustness.measure_input_sensitivity

Test response stability to input variations and perturbations

Server ContextForge MCP Gateway jrmatherly/mcp-context-forge
Category Execute
Risk class High
Parameters 00 required

What robustness.measure_input_sensitivity does on ContextForge MCP Gateway

AI agents invoke robustness.measure_input_sensitivity to trigger actions in ContextForge MCP Gateway. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

Why robustness.measure_input_sensitivity needs a policy

This tool executes a testing/probing operation against a service or model, sending multiple input variations to measure stability. It triggers external operations whose effects depend on arguments (the inputs being tested). It doesn't merely read static data — it actively perturbs inputs and observes responses, which is an Execute-class action.

From the tool's definition 'Test response stability to input variations and perturbations' — actively runs tests by sending input variations/perturbations to a service

Questions about robustness.measure_input_sensitivity

What does the robustness.measure_input_sensitivity tool do? +

Test response stability to input variations and perturbations. It is categorised as a Execute tool in the ContextForge MCP Gateway MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on robustness.measure_input_sensitivity? +

Register the ContextForge MCP Gateway MCP server in PolicyLayer and add a rule for robustness.measure_input_sensitivity: 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.

What risk level is robustness.measure_input_sensitivity? +

robustness.measure_input_sensitivity is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit robustness.measure_input_sensitivity? +

Yes. Add a rate_limit block to the robustness.measure_input_sensitivity 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.

How do I block robustness.measure_input_sensitivity completely? +

Set action: deny in the PolicyLayer policy for robustness.measure_input_sensitivity. 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.

What MCP server provides robustness.measure_input_sensitivity? +

robustness.measure_input_sensitivity 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.