Inspect the current goal session: condition, turn count, elapsed time, and last evaluation.
AI agents call get_status to retrieve information from Goal Engine 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 goal session state (condition, turn count, elapsed time, last evaluation) with no side effects. It is purely informational and matches the 'Read' category pattern of retrieving or querying data without side effects.
From the tool's definition Tool name 'get_status' and description 'Inspect the current goal session' indicate a read-only operation that retrieves and queries the state of a goal-tracking session without modifying or executing anything.
Attacks that exploit this kind of access
Inspect the current goal session: condition, turn count, elapsed time, and last evaluation. It is categorised as a Read tool in the Goal Engine MCP Server, which means it retrieves data without modifying state.
Register the Goal Engine MCP server in PolicyLayer and add a rule for get_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 Goal Engine. Nothing to install.
get_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_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_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_status is provided by the Goal Engine MCP server (melihzafer/mcp-goal). 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 →