plan_table
AI agents call plan_table as a supporting operation in Asset Aware workflows.
With no description available, the tool's function must be inferred from its name alone. 'plan_table' could mean planning/structuring a table (Write), reading/analyzing a table (Read), or something else entirely. Given the server context of PDF asset analysis and knowledge graph integration, it may relate to planning extraction of table assets, which would be Read.
From the tool's definition Tool name is 'plan_table' and description is empty or uninformative.
Attacks that exploit this kind of access
plan_table. It is categorised as a Other tool in the Asset Aware MCP Server, which means it performs auxiliary operations.
Register the Asset Aware MCP server in PolicyLayer and add a rule for plan_table: 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 Asset Aware. Nothing to install.
plan_table is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the plan_table 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 plan_table. 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.
plan_table is provided by the Asset Aware MCP server (u9401066/asset-aware-mcp). 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 →