Exclusive feature tool available only to tenant B.
AI agents call get_tenant_b_exclusive_feature to retrieve information from Mcp Plexus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get' prefix strongly suggests a read operation that retrieves or queries tenant B-specific data without side effects. The tool appears designed for access control within a multi-tenant system.
From the tool's definition Tool name 'get_tenant_b_exclusive_feature' uses 'get' verb indicating data retrieval. Description states it is an 'exclusive feature available only to tenant B' with no mention of modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access get_tenant_b_exclusive_feature gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Plexus, and nothing reaches the server without passing your rules. This is the rule we recommend for get_tenant_b_exclusive_feature:
{
"version": "1",
"default": "deny",
"tools": {
"get_tenant_b_exclusive_feature": {}
}
}get_tenant_b_exclusive_feature is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Exclusive feature tool available only to tenant B. It is categorised as a Read tool in the Mcp Plexus MCP Server, which means it retrieves data without modifying state.
Register the Mcp Plexus MCP server in PolicyLayer and add a rule for get_tenant_b_exclusive_feature: 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 Mcp Plexus. Nothing to install.
get_tenant_b_exclusive_feature 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_tenant_b_exclusive_feature 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_tenant_b_exclusive_feature. 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_tenant_b_exclusive_feature is provided by the Mcp Plexus MCP server (super-i-tech/mcp_plexus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 Mcp Plexus tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
11 Mcp Plexus tools catalogued and risk-classified — across an index of 42,500+ MCP servers.