Run a fake internal architecture check for a service.
AI agents invoke run_architecture_check to trigger actions in Rabobank MCP Training Demo. 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.
This tool executes an architecture check operation on internal banking systems/services. While described as 'fake', it demonstrates execution of external operations typical of banking infrastructure.
From the tool's definition Tool name 'run_architecture_check' with verb 'run' indicates execution of an operation. Description states it 'Run[s] a fake internal architecture check', confirming it triggers an external operation whose effects depend on arguments and context.
Attacks that exploit this kind of access
Run a fake internal architecture check for a service. It is categorised as a Execute tool in the Rabobank MCP Training Demo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Rabobank MCP Training Demo MCP server in PolicyLayer and add a rule for run_architecture_check: 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 Rabobank MCP Training Demo. Nothing to install.
run_architecture_check is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_architecture_check 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 run_architecture_check. 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.
run_architecture_check is provided by the Rabobank MCP Training Demo MCP server (remseymailjard/rabobank-mcp-training). 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 →