Fetch partner profile information from QA environment based on the provided email ID.
AI agents call invoke_partner_profileQA to retrieve information from Agentforce MCP Integration Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves/fetches partner profile data from a QA environment. This is a read-only operation with no side effects. Severity is low since it targets a QA (non-production) environment, though it does access potentially sensitive partner profile information via email ID lookup.
From the tool's definition Fetch partner profile information from QA environment based on the provided email ID
Attacks that exploit this kind of access
Fetch partner profile information from QA environment based on the provided email ID. It is categorised as a Read tool in the Agentforce MCP Integration Server MCP Server, which means it retrieves data without modifying state.
Register the Agentforce MCP Integration Server MCP server in PolicyLayer and add a rule for invoke_partner_profileQA: 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 Agentforce MCP Integration Server. Nothing to install.
invoke_partner_profileQA 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 invoke_partner_profileQA 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 invoke_partner_profileQA. 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.
invoke_partner_profileQA is provided by the Agentforce MCP Integration Server MCP server (santhoshsantomcp/mcpnewtest). 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 →