Fetch required fields, optional fields, and example payloads for a workflow (GET /v1/workflows/{workflow}/schema).
AI agents call get_workflow_schema to retrieve information from Sentinel Signal MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves structural/metadata information about healthcare claims workflows to enable proper payload composition. It performs a read-only query (GET request) against a schema endpoint and returns static configuration data. No data is modified, deleted, or executed.
From the tool's definition Tool fetches schema metadata including 'required fields, optional fields, and example payloads' for a workflow using a GET endpoint. This is purely informational retrieval with no modification, execution, or side effects.
Attacks that exploit this kind of access
Fetch required fields, optional fields, and example payloads for a workflow (GET /v1/workflows/{workflow}/schema). It is categorised as a Read tool in the Sentinel Signal MCP MCP Server, which means it retrieves data without modifying state.
Register the Sentinel Signal MCP server in PolicyLayer and add a rule for get_workflow_schema: 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 Sentinel Signal MCP. Nothing to install.
get_workflow_schema 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 get_workflow_schema 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 get_workflow_schema. 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.
get_workflow_schema is provided by the Sentinel Signal MCP server (sentinelsignal/sentinel-signal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →