AI agents call get_job_history to retrieve information from PeopleSoft MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix and the pattern of sibling tools strongly suggest this retrieves historical job assignment data without modifying it. In an HR context, accessing job history is a non-destructive read operation. Confidence is slightly lowered (0.85 rather than higher) because the description is empty, but the tool name and server context provide sufficient evidence.
From the tool's definition Tool name 'get_job_history' indicates a retrieval operation. The sibling tools on this server (get_accumulator_balances, get_beneficiaries, get_employee, get_payment_info, get_org_chart) all follow a 'get_*' pattern consistent with read-only data retrieval…
Documented attack patterns abuse exactly the kind of access get_job_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PeopleSoft MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_job_history:
{
"version": "1",
"default": "deny",
"tools": {
"get_job_history": {}
}
}get_job_history 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_job_history. It is categorised as a Read tool in the PeopleSoft MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PeopleSoft MCP Server MCP server in PolicyLayer and add a rule for get_job_history: 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 PeopleSoft MCP Server. Nothing to install.
get_job_history 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_job_history 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_job_history. 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_job_history is provided by the PeopleSoft MCP Server MCP server (rgrz/peoplesoft-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PeopleSoft 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.
23 PeopleSoft MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.