AI agents call get_session_status to retrieve information from Agentforce MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about an existing session without modifying, deleting, or executing any operations. It is a straightforward read operation that queries session state. The severity is low because knowing session status poses minimal risk even if accessed inappropriately—it reveals status metadata but does not enable further actions without additional tools.
From the tool's definition Tool name is 'get_session_status' and description states 'Get the status of the current session.' The verb 'get' and the read-only nature of retrieving session status information indicates a query operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_session_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agentforce MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_session_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_session_status": {}
}
}get_session_status 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.
Get the status of the current session. It is categorised as a Read tool in the Agentforce MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Agentforce MCP Server MCP server in PolicyLayer and add a rule for get_session_status: 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 Server. Nothing to install.
get_session_status 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_session_status 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_session_status. 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_session_status is provided by the Agentforce MCP Server MCP server (xlengelle-sf/agentforce-mcp-xlengelle). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Agentforce MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Agentforce MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.