The shared fictional engagement narrative that anchors every example.
AI agents call get_engagement_context to retrieve information from Procurement Graph without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries contextual narrative data for an engagement. It has no capability to modify, delete, or execute operations—it only fetches and returns existing narrative context. The blast radius of misuse is minimal, as providing incorrect context would merely confuse rather than cause harm, making this a straightforward Read operation with low severity.
From the tool's definition Tool name 'get_' and description 'shared fictional engagement narrative' indicate a retrieval operation that returns contextual information without modification or side effects.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The shared fictional engagement narrative that anchors every example. It is categorised as a Read tool in the Procurement Graph MCP Server, which means it retrieves data without modifying state.
Register the Procurement Graph MCP server in PolicyLayer and add a rule for get_engagement_context: 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 Procurement Graph. Nothing to install.
get_engagement_context 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_engagement_context 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_engagement_context. 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_engagement_context is provided by the Procurement Graph MCP server (mfbaig35r/procurement-graph). 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 →