AI agents call correlate_projects to retrieve information from Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to correlate or match projects between Ignition SCADA and Studio 5000 PLC systems, which is a data analysis/querying operation with no indicated ability to modify, delete, or execute external code. The empty description reduces confidence slightly, but the name and server's stated purpose (trace signal chains, find gaps) suggest read-only analysis.
From the tool's definition Tool name 'correlate_projects' suggests comparing/analyzing projects; server context indicates tracing and correlating SCADA/PLC tags for commissioning validation.
Attacks that exploit this kind of access
correlate_projects. It is categorised as a Read tool in the Bridge MCP Server, which means it retrieves data without modifying state.
Register the Bridge MCP server in PolicyLayer and add a rule for correlate_projects: 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 Bridge. Nothing to install.
correlate_projects 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 correlate_projects 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 correlate_projects. 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.
correlate_projects is provided by the Bridge MCP server (nodeblue-ai/bridge-mcp-server). 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 →