AI agents call get_schedule to retrieve information from JoeMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves project schedule data without modifying, deleting, or executing any operations. It is a simple data retrieval function with no side effects, fitting the 'Read' category. Severity is low because accessing schedule data has minimal blast radius—it does not expose financial information directly, does not execute code, and does not modify system state.
From the tool's definition Tool name 'get_schedule' and description 'Get full schedule data for a specific project' indicate a retrieval operation with no modification, deletion, or execution of external actions.
Attacks that exploit this kind of access
Get full schedule data for a specific project. It is categorised as a Read tool in the JoeMCP MCP Server, which means it retrieves data without modifying state.
Register the Joe MCP server in PolicyLayer and add a rule for get_schedule: 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 JoeMCP. Nothing to install.
get_schedule 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_schedule 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_schedule. 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_schedule is provided by the Joe MCP server (lumberjack-so/joemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_schedule is one line of Joe's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →