AI agents call toolfunction as a supporting operation in OfficeMCP workflows.
The description is completely empty and the name 'toolfunction' is generic and uninformative. Given the server context (Office automation via COM interface), this could potentially be anything from reading data to executing commands, but there is insufficient evidence to classify it accurately.
From the tool's definition Tool name is 'toolfunction' with an empty description, providing no information about what it does.
Documented attack patterns abuse exactly the kind of access toolfunction gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OfficeMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for toolfunction:
{
"version": "1",
"default": "deny",
"tools": {
"toolfunction": {
"limits": [
{
"counter": "toolfunction_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}toolfunction gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
toolfunction. It is categorised as a Other tool in the OfficeMCP MCP Server, which means it performs auxiliary operations.
Register the Office MCP server in PolicyLayer and add a rule for toolfunction: 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 OfficeMCP. Nothing to install.
toolfunction 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 toolfunction 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 toolfunction. 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.
toolfunction is provided by the Office MCP server (officemcp/officemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 OfficeMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
16 OfficeMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.